review-comment
Skill6 starsChanged 2 months agoMITView on GitHub
Post, update, or reply to line-specific pull request review comments on GitHub. Use when the user wants to leave feedback on a PR, mention a CI failure tied to a file, reply to an existing review thread, or edit a review comment so it sounds like a human reviewer. The skill targets comments attached to specific diff lines, not top-level PR issue comments.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- moisesrj97/skillstheir own version, first seen Nov 8, 2026
- udecode/platetheir own version, first seen Nov 1, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- udecode/plate★ 17ksame name
- moisesrj97/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- commitSkill
- gh-stackSkill
- grade-itSkill
- hygieneSkill
- install-anti-slopSkill
- principle-prove-it-worksSkill
- react-doctorSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 6 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 33
Check gh auth status first.
- Very specific: line 39
Prefer the gh CLI for creating and editing comments.
- Distinctive: line 40
Never print, quote, or paste a token in the final reply.
- Very specific: line 52
Read the selected file's patch.
- Very specific: line 55
Check for an existing review comment on the same lines, paginated the same way: gh api --paginate …
- Distinctive: line 106
Update an existing line comment's body (JSON body avoids quoting issues.
- Distinctive: line 119
No meta-phrases like "Verified." or "I checked the code and..."
- Distinctive: line 121
Use the user's own file and symbol names.
- Distinctive: line 122
If CI is failing on the same file, mention it in a separate paragraph and give the exact step and the fix command.
- Distinctive: line 141
Do not read or expose tokens.
- Very specific: line 144
Always list files and comments with --paginate.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Review comment
Goal: leave clear, line-specific pull request review comments that read like a human reviewer wrote them — with a "thanks", concrete evidence, and a concrete ask.
When to use
- The user asks to post a review comment, leave line feedback, reply to a review thread, or update an existing review comment.
- The feedback is tied to a specific file and line(s) in a PR diff, not a general PR-level comment.
- The user wants the comment to include CI findings, real fixtures, or brand-casing examples.
What it is
This is a pull request review comment (also called an inline review comment). It appears on the Files changed tab and is attached to a specific diff hunk. It is different from:
- a top-level PR issue comment (conversation tab), or
- a review summary (the
pullrequestreview-...object that can hold many line comments).
The body is GitHub-flavored Markdown. Use single backticks for short identifiers and snippets; triple backticks only for multi-line blocks.
Authentication
Check
gh auth statusfirst. If it is not green, re-register with the keyring token without printing the value:gh auth token -h github.com -u <github-username> 2>/dev/null | gh auth login --with-token- Prefer the
ghCLI for creating and editing comments. The GitHub MCP server can add replies (add_reply_to_pull_request_comment) but cannot edit an existing review comment. - Never print, quote, or paste a token in the final reply.
Workflow
- Identify the target.
Get the PR diff for the file. Paginate both list calls so large PRs are fully covered —
gh api --paginatemerges the JSON array pages into one array:gh api --paginate /repos/{owner}/{repo}/pulls/{number}/files | \ jq '.[] | select(.filename == "apps/web/src/providerModelOptions.ts")'Read the selected file's
patch.- Map the code location to diff line numbers. Added and context lines use side
RIGHTwith new-file line numbers; deleted lines use sideLEFTwith old-file line numbers. - Check for an existing review comment on the same lines, paginated the same way:
gh api --paginate /repos/{owner}/{repo}/pulls/{number}/comments. The commentidis the number after#discussion_r.
- Write the body like a reviewer, not a status report.
- Open with thanks and what is right about the PR.
- Explain the specific regression or concern, quoting the code with inline backticks.
- Give real evidence: a fixture, a discovered model name, a CI failure, or a local reproduction.
- State the user-visible effect, not only the code behavior.
- Close with a question or a concrete suggestion.
- Post, reply, or update.
New single-line comment (no range: omit
start_lineandstart_side):gh api -X POST /repos/{owner}/{repo}/pulls/{number}/comments \ -f path="apps/web/src/providerModelOptions.ts" \ -f line=175 \ -f side=RIGHT \ -f body="Thank you for the PR..."New multi-line comment (
start_sidemust matchside):gh api -X POST /repos/{owner}/{repo}/pulls/{number}/comments \ -f path="apps/web/src/providerModelOptions.ts" \ -f line=175 \ -f start_line=174 \ -f side=RIGHT \ -f start_side=RIGHT \ -f body="Thank you for the PR..."New comment on a deleted line (
side=LEFT, old-file line number):gh api -X POST /repos/{owner}/{repo}/pulls/{number}/comments \ -f path="apps/web/src/providerModelOptions.ts" \ -f line=120 \ -f side=LEFT \ -f body="This block was removed..."Reply to an existing thread (adds a threaded response; never PATCH for this):
gh api -X POST /repos/{owner}/{repo}/pulls/{number}/comments/{id}/replies \ -f body="Good catch, fixed in the follow-up commit."The GitHub MCP server can also add replies (
add_reply_to_pull_request_comment).Update an existing line comment's body (JSON body avoids quoting issues; PATCH edits the body only and never adds a reply):
jq -n --arg body "$body" '{body: $body}' | \ gh api -X PATCH /repos/{owner}/{repo}/pulls/comments/{id} --input -
- Verify.
- Fetch the comment:
gh api /repos/{owner}/{repo}/pulls/comments/{id}. - Open the
html_urland confirm the text, line range, and formatting.
- Fetch the comment:
Style
- No meta-phrases like "Verified." or "I checked the code and..."
- One concern per comment.
- Use the user's own file and symbol names; do not invent paths.
- If CI is failing on the same file, mention it in a separate paragraph and give the exact step and the fix command.
Example
Thank you for the PR. The `glm` and `deepseek` casing fixes are right, but `rawNameIsIdentifier` looks like it will regress provider-branded names that aren't in `MODEL_TOKEN_DISPLAY_NAMES`.
OpenCode serves `opencode/minimax-m2.5-free` with `name: "MiniMax M2.5 Free"`. With this check, `modelDisplayIdentity("MiniMax M2.5 Free")` equals `modelDisplayIdentity("minimax-m2.5-free")`, so the provider-supplied name is discarded and the fallback is `humanizeModelSlug`. That function only restores casing for `deepseek` and `glm`, so `minimax` becomes `Minimax` and the rendered label is `Minimax M2.5 Free` — losing the brand casing.
Same issue clobbers `kimi-for-coding/k2p6` with `name: "K2P6"` → `K2p6`.
Also, `Static Checks (fast)` is failing on the `Format` step (`bun run fmt:check` / `oxfmt --check`). It flags formatting in 3 files: `apps/web/src/components/chat/ProviderModelPicker.browser.tsx`, `apps/web/src/providerModelOptions.ts`, and `packages/shared/src/model.ts`. Running `bun run fmt` will fix the import/chain indentation.
Could we keep the provider's exact casing when the raw name is only a casing/separator variant, or expand the token table to cover `minimax`, `kimi`, and other provider brands discovery is known to return?Caveats
gh auth statusmust be green before anygh apiorgh prcall.- Do not read or expose tokens. Use the keyring re-register flow above.
- The GitHub MCP server can add a reply to an existing review comment but cannot
PATCHan existing one; useghfor edits. - A comment that needs a line range must pass both
lineandstart_linewith matchingsideandstart_side. A single-line comment passes onlylineandside. - Always list files and comments with
--paginate; first-page-only lookups miss files and threads on large PRs and cause duplicate replies.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

