review-findings

Featured

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.

Code & Development 3,438 stars 500 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
71
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill 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 1. Runs the SIGN IN checklist 2. Reads the review report and understands each finding's root cause 3. Plans fix order: Critical first, then Warnings 4. Implements fixes with updated tests for each finding 5. Scans for dead code after all fixes 6. Runs Implementation Complete and Pre-Delivery checklists (TIME OUT) 7. Verifies every Critical finding addressed, every Warning addressed or deferred with justification 8. 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 `docs/reviews/` is used - The agent understands root causes before writing any fix - Conflicting fixes are identified and planned around during the pre-fix phase

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

Code & Development Listed

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.

1 Updated 4 days ago
renatodvc
AI & Automation Listed

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.

3 Updated today
chrislacey89
Code & Development Listed

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).

2 Updated 3 weeks ago
carinyaparc