review-findings
FeaturedAddresses 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
Quality Score: 94/100
Skill Content
Details
- Author
- davepoon
- Repository
- davepoon/buildwithclaude
- Created
- 1 years ago
- Last Updated
- 2 days ago
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
fix-findings
Fix the findings from an independent-review report. Follow-on to the independent-review skill, but never run it automatically after a review: the user reads the report first and decides. Only run when the user explicitly invokes /address-findings or explicitly asks to address the review findings.
fix-findings
Invoked helper skill for fixing the /pre-merge findings a human has already chosen, with a fresh sub-agent writing each fix and a second fresh sub-agent trying to break it. User-invoked only — type /fix-findings <numbers> after picking findings from a review. Not for choosing which findings to act on, not for stamping review currency, and not for merging.
code-review-fix
Use when the user wants to address, action, or fix findings from a code review — their own working diff reviewed by code-review, a reviewer's comments on a PR or MR, or a pasted list of issues. Triggers on "fix the review findings", "address the review feedback", "action the blocking issues", "apply the review comments". Optionally scoped to an action tier (blocking, warning, all). Makes targeted, behaviour-preserving changes, runs the project's validation suite, and commits in logical units. Do NOT use to perform a review (code-review), to implement new work or features (implement), to address UX or design-fidelity findings (ux-design-fix), or to open a PR/MR (merge-request).