x-fix-pr
Reads PR review comments and fixes actionable ones automatically. Detects PR from argument or branch, classifies comments (actionable/suggestion/question/praise), implements fixes, and commits with proper conventional commit messages.
- License 许可
- MIT
- 最近更新
- 2026-10-27
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- x-fix-pr
- description
- Reads PR review comments and fixes actionable ones automatically. Detects PR from argument or branch, classifies comments (actionable/suggestion/question/praise), implements fixes, and commits with proper conventional commit messages.
- allowed-tools
- Read, Write, Edit, Bash, Grep, Glob
- argument-hint
- [PR-number]
- context-budget
- medium
- user-invocable
- true
- requires-capabilities
- []
02 资源文件 1
- 参考文档README.md1.7 KB
03 SKILL.md 正文
Global Output Policy
- Language: English ONLY.
- Tone: Technical, Direct, and Concise.
- Efficiency: Remove all conversational fillers and greetings to save tokens.
Skill: Fix PR Comments
Purpose
Automates the process of addressing PR review comments for {{PROJECT_NAME}}. Reads all review comments from a pull request, classifies them by type, and implements fixes for actionable feedback.
Triggers
/x-fix-pr— fix comments on current branch's PR/x-fix-pr 123— fix comments on PR #123
Parameters
| Parameter | Required | Description |
|---|---|---|
PR-number |
No | PR number to process. If omitted, detect from current branch. |
Workflow
1. DETECT -> Identify PR (argument or branch)
2. FETCH -> Get all review comments via GitHub CLI
3. CLASSIFY -> Categorize each comment (actionable/suggestion/question/praise/resolved)
4. FIX -> Implement fixes for actionable comments
5. VERIFY -> Compile and test after each fix
6. REPLY -> Reply to each comment thread in PT-BR (fix summary or rejection reason)
7. COMMIT -> Commit with conventional commit message
8. REPORT -> Summarize actions taken
Step 1 — Detect PR
Determine which PR to process:
# If argument is a number, use it directly
PR_NUMBER=$1
# If no argument, detect from current branch
if [ -z "$PR_NUMBER" ]; then
gh pr view --json number --jq '.number'
fi
If no PR found, abort: No PR found for current branch. Provide a PR number as argument.
Step 2 — Fetch Review Comments
# Get all review comments (not issue comments)
gh api repos/{owner}/{repo}/pulls/{PR_NUMBER}/comments \
--jq '.[] | {id: .id, path: .path, line: .line, body: .body, user: .user.login, created_at: .created_at}'
# Also get PR review threads for context
gh api repos/{owner}/{repo}/pulls/{PR_NUMBER}/reviews \
--jq '.[] | {id: .id, state: .state, body: .body, user: .user.login}'
Step 3 — Classify Comments
For each comment, classify into one of:
| Type | Description | Action |
|---|---|---|
| Actionable | Clear request to change code (fix bug, rename, refactor) | Implement the fix |
| Suggestion | Optional improvement with rationale | Implement if aligns with project standards |
| Question | Reviewer asking for clarification | Skip (requires human response) |
| Praise | Positive feedback | Skip |
| Resolved | Already addressed or outdated | Skip |
Classification rules:
- Contains "please change", "should be", "must", "fix", "bug", "wrong" — Actionable
- Contains "consider", "maybe", "could", "suggestion", "nit" — Suggestion
- Contains "?", "why", "what", "how does" — Question
- Contains "LGTM", "nice", "good", "great" — Praise
- Thread is marked as resolved — Resolved
Step 4 — Implement Fixes
For each actionable/suggestion comment:
-
Read the file at the specified path and line:
# Comment metadata provides path and line cat -n {path} | sed -n '{line-5},{line+5}p' -
Understand the reviewer's request
-
Implement the fix using Edit tool
-
If the fix requires understanding broader context, read surrounding code first
Ordering: Process comments file-by-file to minimize context switching. Within a file, process top-to-bottom to avoid line number shifts.
Step 5 — Verify
After each fix (or batch of fixes per file):
{{COMPILE_COMMAND}}
{{TEST_COMMAND}}
If compilation fails, revert the last change and try an alternative approach. If tests fail, analyze the failure and adjust the fix.
Step 6 — Reply to Comments (PT-BR)
After each comment is processed (fixed, skipped, or rejected), reply to the review comment thread in Portuguese (pt-BR) explaining the action taken.
Reply command:
# Reply to an inline review comment thread
gh api repos/{owner}/{repo}/pulls/{PR_NUMBER}/comments/{comment_id}/replies \
-f body="{message_in_portuguese}"
Reply templates by classification:
| Classification | Reply Template (PT-BR) |
|---|---|
| Actionable (fixed) | Corrigido. {descricao da alteracao feita}. Commit: {short_hash} |
| Suggestion (accepted) | Sugestao aceita. {descricao da alteracao feita}. Commit: {short_hash} |
| Suggestion (rejected) | Sugestao analisada, mas nao aplicada. Motivo: {razao tecnica pela qual nao faz sentido no contexto atual} |
| Actionable (rejected) | Observacao analisada, mas nao faz sentido neste contexto. Motivo: {explicacao tecnica detalhada} |
| Actionable (failed) | Tentei corrigir, mas a alteracao causou falha na compilacao/testes. Necessita intervencao manual. |
| Question | (no reply — requires human response) |
| Praise | (no reply) |
| Resolved | (no reply — already resolved) |
Rules:
- ALL replies MUST be in Portuguese (pt-BR)
- Be specific: describe exactly what was changed and why
- When rejecting, provide technical justification (reference project rules, architecture constraints, or coding standards)
- Include commit hash when a fix was applied
- Never reply to praise or already-resolved comments
Examples:
Fix applied:
Corrigido. Renomeei a variavel `d` para `elapsedTimeInMs` conforme padrao de naming do projeto. Commit: abc1234
Suggestion rejected:
Sugestao analisada, mas nao aplicada. Motivo: o metodo precisa ser publico porque implementa a interface Assembler, que define o contrato do pipeline. Tornar package-private quebraria o polimorfismo.
Comment doesn't make sense:
Observacao analisada, mas nao faz sentido neste contexto. Motivo: o null check sugerido e desnecessario aqui — o parametro vem de um Optional.orElseThrow() na linha 42, garantindo que nunca sera null neste ponto.
Step 7 — Commit
After all fixes for a logical group are verified:
git add {modified-files}
git commit -m "fix({scope}): address PR review comments
- {summary of change 1}
- {summary of change 2}
Addresses review comments on PR #{PR_NUMBER}"
Scope should match the module/layer affected (e.g., domain, api, config).
Step 8 — Report
Output a summary table:
## PR Review Comments — Fix Report
**PR:** #{PR_NUMBER}
**Total comments:** N
**Processed:** M
| # | File | Line | Type | Action | Status | Reply |
|---|------|------|------|--------|--------|-------|
| 1 | src/main/Foo.java | 42 | Actionable | Renamed variable | Fixed | Replied |
| 2 | src/main/Bar.java | 15 | Suggestion | Added null check | Fixed | Replied |
| 3 | src/main/Baz.java | 20 | Actionable | — | Rejected | Replied |
| 4 | src/main/Baz.java | 88 | Question | — | Skipped | — |
| 5 | src/main/Qux.java | 3 | Praise | — | Skipped | — |
### Questions Requiring Human Response
- **src/main/Baz.java:88** (@reviewer): "Why is this method public?"
Error Handling
| Scenario | Action |
|---|---|
| PR not found | Abort with message |
| No comments on PR | Report "No review comments found" |
| Comment references deleted file | Skip with warning |
| Fix causes compilation failure | Revert and report as "Unable to fix automatically" |
| Fix causes test failure | Revert and report as "Fix caused regression" |
| API rate limit | Wait and retry (max 3 attempts) |
Integration Notes
| Skill | Relationship | Context |
|---|---|---|
x-implement-story |
called-by | Invoked during Phase 4 (fix review comments) |
x-fix-epic-pr |
called-by | Batch mode processes multiple PRs from an epic |
x-push-branch |
calls | Uses Conventional Commits format for fix commits |
x-review-codebase |
reads | Processes comments produced by specialist reviews |
04 同仓库更多 Skills
x-parallel-eval
Detects and classifies file-collision risks between work units (tasks, stories, or epic phases) before parallel execution. Reads ## File Footprint blocks produced by x-task-plan / x-story-plan, applies the parallelism-heuristics knowledge pack (hard / regen / soft categories + hotspot overrides), and emits a collision matrix + serialization recommendation in Markdown (default) or JSON.
parallelism-heuristics
Canonical catalog of file-collision heuristics for parallel task, story, and epic execution. Defines the File Footprint block format, the three Conflict Categories (hard / regen / soft), a hotspot list of high-contention paths, and the degrade-with-warning policy. Consumed by x-task-plan, x-story-plan, x-epic-map, x-parallel-eval, and x-dev-*-implement.
x-watch-pr-ci
Polls a PR's CI checks and Copilot review status, blocking until checks complete or timeout. Returns one of 8 stable exit codes (SUCCESS=0, CI_PENDING_PROCEED=10, CI_FAILED=20, TIMEOUT=30, PR_ALREADY_MERGED=40, NO_CI_CONFIGURED=50, PR_CLOSED=60, PR_NOT_FOUND=70). Writes a versioned state-file for session resume.
x-validate-docs
Documentation freshness gate: validates 6 dimensions (readme, api-specs, grpc-proto, adr, skill-docs, system-architecture) against code changes in a PR. Stack-aware — only validates targets declared/auto-detected from ProjectConfig.documentation.targets. Returns exit non-zero on staleness; produces structured report.
x-update-system-architecture
Incrementally updates docs/architecture/system.md after an epic completes. Appends new entries to the Decision Log (§11) using x-internal-write-report --append (dedup by ## ID: marker) and surgically inserts component/integration changes into sections 1-10 via Edit. Idempotent: re-running with the same epic produces a byte-identical system.md.
x-update-architecture
Incrementally updates the service architecture document with changes from architecture plans. Adds new components, integrations, flows, and ADR references without rewriting existing content. Use after implementation to keep architecture documentation current.