Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Address code review feedback by evaluating validity and fixing issues โ supports local agent feedback and GitHub PR threads. Triggers: "fix the review feedback", "address PR comments".
user-invocable
true
context
fork
fix-code-review-feedback
Address code review feedback from local review agents or GitHub PRs.
This skill fixes feedback, not generates it. Use code review agents to get feedback first, then use this skill to address it.
Core Principles
Agent time is cheap. Tech debt is expensive.
Fix everything valid - Including nitpicks. Don't carry debt forward.
Reviewers can be wrong - Verify concerns exist before fixing.
Quote feedback in replies - Provide context for what was addressed.
Mode Detection
Trigger
Mode
Code review agent just provided feedback in conversation
Local Mode (auto-invoke)
/fix-code-review-feedback with no args
PR Mode - Full (current branch's PR)
User provides link to specific comment/thread
PR Mode - Targeted (only that feedback)
Ambiguous
Ask user
Targeted mode: When user provides a specific feedback URL, ONLY address that feedback. Do not fetch or evaluate other PR feedback unless user explicitly asks.
Local Mode (Post-Review Agent)
When a code review agent has just provided feedback:
1. Parse Feedback
Extract issues from the conversation - typically file:line references with descriptions.
2. Evaluate Each Item
Category
Action
โ Valid concern
Fix (possibly with better approach than suggested)
โ ๏ธ Valid concern, bad suggestion
Fix differently
โ Invalid (misread code, already handled)
Skip with explanation
๐ค Uncertain
Ask user
3. Fix All Valid Issues
Read files, implement fixes, verify they work. Do not commit yet.
4. Batch Commit
After ALL fixes are implemented, create a single commit:
git add -A
git commit -m "Address code review feedback
- [list all changes]"
git add -A
git commit -m "Address PR review feedback
- [list all changes]
- [threads resolved]"
git push
GitHub CLI Usage
Always use gh CLI. Fall back to GitHub MCP only if gh fails.
Prefer high-level commands. Only use gh api when required:
Operation
Command
Why
PR metadata
gh pr view --json ...
High-level, efficient
Add PR comment
gh pr comment --body ...
High-level, efficient
Fetch review threads
gh api graphql
Required - no CLI equivalent
Reply to thread
gh api graphql
Required - no CLI equivalent
Resolve thread
gh api graphql
Required - no CLI equivalent
Do NOT use gh api for operations that have high-level equivalents.
Validity Evaluation
1. Can I reproduce the concern?
NO โ Skip (explain why)
2. Is concern still relevant to current code?
NO โ Skip (explain code changed)
3. Would the fix improve the code?
YES โ Implement
NO but concern valid โ Implement better alternative
NO and concern wrong โ Skip (explain)
When to ask user: Architectural changes, security implications, conflicting conventions, business logic decisions.
Examples
PR Mode - Full
User: /fix-code-review-feedback
Agent:
Fetching feedback for current branch's PR (#123)...
Found 3 unresolved threads:
1. โ "Missing null check on user.email"
โ Adding null check at auth.js:45
2. โ "Unused import: lodash"
โ Removing unused import
3. โ "No error handling for API call"
โ Invalid: try/catch exists at line 78. Replying with explanation.
Committed and pushed. 2 fixed, 1 declined.
PR Mode - Targeted
User: /fix-code-review-feedback https://github.com/org/repo/pull/123#discussion_r1234567
Agent:
Fetching specific feedback...
Thread: "Missing null check on user.email"
โ Valid concern. Adding null check at auth.js:45
Replied, resolved thread, committed and pushed.
Local Mode (Auto-Invoked)
[After code review agent provides feedback in conversation]
Agent:
Processing review feedback...
1. โ Race condition at api.ts:23 โ Adding mutex lock
2. โ Missing type at api.ts:45 โ Adding `: Error` annotation
All issues addressed and committed.
