gh-address-comments skillA
This file is byte-identical to the first copy the registry indexed, one of 3 copies on public GitHub. Same content hash, same audit grade.
gh-address-comments is agent-read markdown (skill) from yeaight7/agent-powerups: Address actionable GitHub pull request review feedback. Use when the user wants to inspect unresolved review threads, requested changes, or inline review comments on a PR, then implement selected fixes..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# GitHub PR Comment Handler Use this skill when the user wants to work through requested changes on a GitHub pull request. Use the GitHub MCP or `gh` CLI for PR metadata and patch context. Treat thread-aware review data as a `gh api graphql` problem — the flat comment surface does not preserve full review-thread state. Run all `gh` commands with elevated network access. If CLI auth is required, confirm `gh auth status` first and ask the user to authenticate with `gh auth login` if it fails. ## Workflow 1. **Resolve the PR.** - If the user provides a repository and PR number or URL, use that directly. - If the request is about the current branch PR, use local git context: `gh pr view --json number,url`. 2. **Inspect review context with thread-aware reads.** - Use `gh api graphql` whenever the task depends on unresolved review threads, inline review locations, or resolution state — it fetches `reviewThreads`, `isResolved`, `isOutdated`, and file/line anchors. - Use flat comment reads only for lightweight top-level PR comment summaries. 3. **Cluster actionable review threads.** - Group comments by file or behavior area. …
Read the whole file at its exact version.
How to install
mdr add yeaight7/agent-powerups/gh-address-comments@git:20260606.48003f5mdr add yeaight7/agent-powerups/gh-address-comments@sha256:0a8c429ff004109aPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_sg6dfuaj7y3jc5eb)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260606.48003f5 latest | 2026-06-06 | 48003f5 | 4,148 B | A | view · diff |
| git:20260430.436d0fb | 2026-04-30 | 436d0fb | 3,656 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4148 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
yeaight7/agent-powerups · 6 stars · license Apache-2.0 · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_sg6dfuaj7y3jc5eb GET https://markdownregistry.com/api/v1/resolve?ref=yeaight7/agent-powerups/gh-address-comments GET https://markdownregistry.com/api/v1/blob/0a8c429ff004109a80ce27e7cc15515a3fca73c2a22ea5b7ce83645ea1f7b652
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from yeaight7/agent-powerups
Every file in yeaight7/agent-powerups