review-pr-comments
Skill12 starsChanged 6 days agoMITView on GitHub
Review and triage PR review comments (from Copilot, bots, or human reviewers) against the actual codebase. Use when a user wants to evaluate the validity, priority, or accuracy of PR review comments before deciding which ones to act on. Also handles applying approved fixes. Triggers on requests like "review all comments in this PR", "evaluate PR feedback", "which PR comments are valid", "apply the PR suggestions".
7 other projects use a version of this.
Adopted by
Most recently taken up by
- MadsVSChristensen/claude-skillstheir own version, first seen Nov 15, 2026
- IBazylchuk/paparats-mcptheir own version, first seen Nov 1, 2026
- rhvdbergh/claude-skillstheir own version, first seen Oct 16, 2026
- learntocloud/learn-to-cloud-apptheir own version, first seen Oct 8, 2026
- latitude-dev/latitude-llmtheir own version, first seen Oct 8, 2026
- DataDog/datadog-agenttheir own version, first seen Oct 8, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- latitude-dev/latitude-llm★ 4.7ksame name
- DataDog/datadog-agent★ 3.8ksame name
- learntocloud/learn-to-cloud-app★ 1.1ksame name
- IBazylchuk/paparats-mcp★ 34same name
- Hey-Diga/dotclaude★ 17same name
- MadsVSChristensen/claude-skills★ 0same name
- rhvdbergh/claude-skills★ 0same 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 repository51 other files it gives its agents.
- agents.mdAGENTS.md
- .agents/skills/react-best-practices/AGENTS.mdAGENTS.md
- .agents/skills/react-native-skills/AGENTS.mdAGENTS.md
- .agents/skills/react-view-transitions/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- agent-initSkill
- agy-delegateSkill
- audit-docsSkill
- code-audit-expertSkill
- computer-diagnosisSkill
- create-builtin-toolSkill
- create-prSkill
- critique-builtin-toolSkill
- doc-auditorSkill
- docxSkill
- extract-log-debugSkill
- feature-refactor-proposalSkill
- gatekeeper-loopSkill
- harbor-harness-improvement-loopSkill
- harness-eval-loopSkill
- i18n-language-standardsSkill
- jobs-trace-analyzerSkill
- lean-builtin-tool-auditorSkill
- libragent-qualitySkill
- libr-delegateSkill
- libr-tool-e2e-harness-loopSkill
- modular-large-file-refactorSkill
- performance-auditSkill
- pptxSkill
- producer-loopSkill
- vercel-react-best-practicesSkill
- vercel-react-native-skillsSkill
- vercel-react-view-transitionsSkill
- readme-showcase-syncSkill
- refactor-builtin-toolSkill
- release-head-self-e2eSkill
- release-managerSkill
- review-local-changesSkill
- science-searchSkill
- setup-wizardSkill
- skill-creatorSkill
- soul-awakeningSkill
- sqlite-analyzerSkill
- sync-pending-approvalsSkill
- tool-creatorSkill
- trace-analyzerSkill
- trace-eval-loopSkill
- vitepress-doc-syncSkill
- worker-loopSkill
- x-cliSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 7 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Use github-pull-request_activePullRequest (or github-pull-request_openPullRequest if not checked out).
- Distinctive: line 26
Read enough context (±20 lines) to understand whether the suggestion is already satisfied, partially applied, or still needed.
- Distinctive: line 28
If a comment references another file as a "pattern" or "example," read that file too to verify the claim.
- Distinctive: line 56
When the user confirms, apply all approved changes using targeted edits (not wholesale file replacement).
- Distinctive: line 60
After all approved fixes have been applied, produce a ready-to-paste agent prompt that verifies the PR's actual runtime behavior inside …
- Distinctive: line 64
After Step 5 completes, OR
- Distinctive: line 65
When the user asks "테스트 프롬프트 만들어줘" / "give me a test prompt"
- Very specific: line 69
Read the PR changes[] diff to identify what runtime behavior changed (not just what code changed).
- Distinctive: line 124
When a comment says "follow the pattern in X:Y-Z", read those lines to confirm the pattern actually exists there before accepting the claim.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Review PR Comments
Systematically pull, evaluate, and optionally apply review comments from a pull request.
Workflow
1. Fetch PR Data
Use github-pull-request_activePullRequest (or github-pull-request_openPullRequest if not checked out).
Extract from the result:
comments[]— inline review comments (attached to files/lines)timelineComments[]— general PR comments (overviews, bots, etc.)changes[]— the actual diff
2. Read Affected Code
For each comment with a file field, read the current file at the referenced location — not just the diff. The diff shows what was changed; the file shows what exists now.
Read enough context (±20 lines) to understand whether the suggestion is already satisfied, partially applied, or still needed.
If a comment references another file as a "pattern" or "example," read that file too to verify the claim.
3. Evaluate Each Comment
For every comment assess:
| Dimension | Questions |
| Valid? | Does the issue actually exist in the current code? Has it already been fixed? |
| Accurate? | Are file paths, line numbers, and named references correct? |
| Priority | Would ignoring it cause a bug / bad UX / policy violation (High), a maintainability issue (Medium), or is it purely stylistic (Low)? |
| Action | Apply immediately / Apply optionally / Skip with reason |
4. Report
Produce a summary table per comment:
| # | File | Key / Location | Valid? | Priority | Action |
|---|------|---------------|--------|----------|--------|
| 1 | foo.tsx | line 29 | ✅ Yes | Medium | Apply |
| 2 | bar.tsx | line 193 | ⚠️ Partial | Low | Optional |Include a short rationale for each verdict. Call out inaccuracies in the comment itself (wrong line numbers, wrong file references) even if the underlying suggestion is valid.
5. Apply Fixes (if instructed)
When the user confirms, apply all approved changes using targeted edits (not wholesale file replacement). Re-read the current file state before editing — it may have changed since the PR was opened.
6. Generate Live Test Prompt (after fixes applied)
After all approved fixes have been applied, produce a ready-to-paste agent prompt that verifies the PR's actual runtime behavior inside LibrAgent.
When to generate:
- After Step 5 completes, OR
- When the user asks "테스트 프롬프트 만들어줘" / "give me a test prompt"
How to construct the prompt:
- Read the PR
changes[]diff to identify what runtime behavior changed (not just what code changed). - For each changed behavior, design a concrete, observable test step the agent can execute with its tools (shell commands, file search, browser, etc.).
- Instruct the agent to report actual output for each step, not just "success/fail."
Template:
다음 변경 사항의 실동작을 순서대로 검증해줘.
## 테스트 N: [변경 이름]
1. [도구 호출 또는 명령]
2. [예상 출력 또는 확인 기준]
3. [엣지 케이스가 있다면 추가 단계]
각 단계의 실제 출력을 그대로 보고해줘.Rules:
- Each test must be fully self-contained (set up its own fixtures if needed).
- Expected output must be concrete and observable — not "should work correctly" but "output contains
./subdir". - Cover the main success path AND at least one error/edge case per change.
- Clean up any temp files/directories created during tests at the end.
Evaluation Heuristics
Mark as High priority if:
- Missing fallback/defaultValue on i18n keys that could surface raw key strings to users
- Type safety violations (unsafe casts, missing validation)
- Logic bugs or race conditions
- Accessibility regressions
Mark as Medium priority if:
- Inconsistency with an established codebase pattern
- Missing error handling that degrades gracefully
- Performance issues under realistic load
Mark as Low / Optional if:
- Purely cosmetic or stylistic (matches one valid style but not the only one)
- Suggestion is already covered by a neighboring line or fallback
- The referenced "pattern" doesn't actually match the claim
Mark as Invalid if:
- The issue no longer exists in the current file state
- The suggestion would introduce a regression
- The referenced example file/line doesn't exist or doesn't demonstrate what is claimed
Notes
- Bot reviewers (Copilot, Jules, etc.) often reference incorrect line numbers — always verify against the actual file.
defaultValuein i18nextt()matters most for plural keys (_one/_othersuffix). For simple interpolation keys that exist in all locale files, it is optional.- When a comment says "follow the pattern in X:Y-Z", read those lines to confirm the pattern actually exists there before accepting the claim.
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.

