github-pr-comments skillA
github-pr-comments is agent-read markdown (skill) from tailcallhq/forgecode: Resolve inline code review comments on a GitHub PR. Use when asked to "resolve review comments", "address PR feedback", "fix PR comments", or "work through review comments". Fetches every inline comment with its surrounding code context, then applies each change systematically..
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 before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
# Resolve Code Review Comments ## 1. Fetch all comments Run the bundled script to get every inline comment with its diff hunk: ```bash bash .forge/skills/resolve-code/scripts/pr-comments.sh [PR_NUMBER] ``` Omit `PR_NUMBER` to use the current branch's PR. Each block in the output contains: - `File :` — file path and line number - `-- code context --` — the diff hunk showing surrounding lines - `-- comment --` — the reviewer's message ## 2. Create a todo item per comment Add one todo for each comment before touching any code. This ensures nothing is missed even when comments span many files. ## 3. Apply each comment Work through todos one at a time. There are two comment types: ### Suggestion block Body starts with ` ```suggestion `. Apply the suggested text verbatim as a replacement for the highlighted lines in the diff hunk. ### Free-form feedback Read the comment in the context of the diff hunk, infer the required change, and implement it. When the intent is ambiguous, make the change that best matches the project's conventions and state the assumption clearly. ## 4. Verify After all comments are addressed, run: ```bash cargo check && cargo nextest run ``` …
Read the whole file at its exact version.
How to install
mdr add tailcallhq/forgecode/github-pr-comments@git:20260402.238a5b9mdr add tailcallhq/forgecode/github-pr-comments@sha256:65f51a4f947a896fPin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
[](https://markdownregistry.com/a/art_svvproeku7hfokk7)
2 badge views in 30 days
Versions
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 (1587 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
tailcallhq/forgecode · 7,637 stars · license Apache-2.0 · pushed 2026-09-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_svvproeku7hfokk7 GET https://markdownregistry.com/api/v1/resolve?ref=tailcallhq/forgecode/github-pr-comments GET https://markdownregistry.com/api/v1/blob/65f51a4f947a896fc12a78ffa42d64307a96be1ffcc26e8c0c6e54dae45e2070
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.