piv-fix-review-findings

Triage code-review findings, fix selected issues with tests, and push fixes to the PR.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/az9713/claude-code-hooks-tutorial --skill piv-fix-review-findings-az9713
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: piv-fix-review-findings
Source: https://github.com/az9713/claude-code-hooks-tutorial/tree/main/skills/.claude/skills/piv-fix-review-findings
Command: npx skills add https://github.com/az9713/claude-code-hooks-tutorial --skill piv-fix-review-findings-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a code review produces a list of findings, it is unclear which issues to fix now, which to defer, and which to ignore. This Skill turns a review into a controlled workflow: triage each finding, fix the chosen ones one at a time with tests, log the rest as issues, and keep the PR up to date. ## Core Features & Use Cases - Structured triage: Sorts findings into fix-now, defer/log-as-issue, needs-manual-review, and won't-fix buckets, asking for direction when scope is unclear. - One-at-a-time fixes with tests: Each accepted fix gets an explanation, the code change, and a test proving it works. - PR synchronization: Commits via the piv-commit skill and pushes so the PR reflects the fixes, then validates with the piv-validate skill. - Use Case: A reviewer leaves 12 comments on your pull request. You run this Skill with the review file, choose to fix 5 now, defer 4 as tracker issues, flag 2 for manual testing, and dismiss 1 as noise — then push the fixes so the review can re-run. ## Quick Start Ask the assistant to triage the findings in your code review file, fix the in-scope issues one at a time with tests, defer the rest as issues, and push the fixes to the PR.

Frequently Asked Questions about piv-fix-review-findings

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix code review findings one at a time?▼

Provide the review file or issue list and a scope direction. The Skill triages findings into fix-now, defer, manual-review, and won't-fix groups, then fixes each accepted item individually with an explanation and a proving test.

How to handle review comments that should not be fixed in this PR?▼

Mark them as deferred during triage. The Skill logs them as tracker issues instead of fixing them, keeping the PR small while ensuring real findings are not lost.

Does this update the pull request after fixing review findings?▼

Yes. If the fixes are on a PR branch, the Skill commits them using the piv-commit skill and pushes so the PR reflects the changes and the review can re-run on the updated code.

What happens if every review finding is deferred?▼

Nothing is pushed because there are no code changes. The Skill ensures all deferred items are logged as issues so they remain tracked for later work.

When should a review finding be flagged for manual testing?▼

Flag anything that requires human inspection or hands-on verification before it can be trusted. The Skill surfaces these items in the final report rather than silently auto-fixing them.