Buildwithclaude review-findings
Addresses and fixes findings from a QA code review. Reads the review report, fixes critical and warning issues, and prepares for re-verification. Delegates to the Forja (Dev) agent.
install
source · Clone the upstream repo
git clone https://github.com/davepoon/buildwithclaude
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/davepoon/buildwithclaude "$T" && mkdir -p ~/.claude/skills && cp -r "$T/plugins/agent-triforce/skills/review-findings" ~/.claude/skills/davepoon-buildwithclaude-review-findings && rm -rf "$T"
manifest:
plugins/agent-triforce/skills/review-findings/SKILL.mdsource content
Review Findings
Addresses and fixes QA findings using the Forja (Dev) agent.
When to Use This Skill
- After receiving a code review from Centinela (QA)
- When a review report has findings that need to be addressed
- Fixing critical and warning issues before re-verification
What This Skill Does
- Runs the SIGN IN checklist
- Reads the review report and understands each finding's root cause
- Plans fix order: Critical first, then Warnings
- Implements fixes with updated tests for each finding
- Scans for dead code after all fixes
- Runs Implementation Complete and Pre-Delivery checklists (TIME OUT)
- Verifies every Critical finding addressed, every Warning addressed or deferred with justification
- Prepares a fix report for QA re-verification
How to Use
Basic Usage
/review-findings
With Specific Review
/review-findings docs/reviews/user-auth-review.md
Example
User:
/review-findings docs/reviews/webhook-system-review.md
Output:
- All Critical findings fixed with tests
- All Warning findings fixed or explicitly deferred with justification
- Fix report documenting what was changed and why
- Ready for QA re-verification
Tips
- If no review is specified, the most recent review in
is useddocs/reviews/ - The agent understands root causes before writing any fix
- Conflicting fixes are identified and planned around during the pre-fix phase