review-findings
The review-findings skill processes QA code review reports by reading findings, prioritizing critical and warning issues, implementing fixes with corresponding tests, and generating a fix report for re-verification. Use this skill after receiving a code review report from QA to systematically address identified issues before submitting work for re-verification.
git clone --depth 1 https://github.com/davepoon/buildwithclaude /tmp/review-findings && cp -r /tmp/review-findings/plugins/agent-triforce/skills/review-findings ~/.claude/skills/review-findingsSKILL.md
# 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
Scans the codebase for dead code, tech debt, outdated dependencies, and code quality issues. Delegates to the Centinela (QA) agent.
Creates a complete product feature specification with acceptance criteria, scope, dependencies, and risks. Delegates to the Prometeo (PM) agent.
Implements a feature from its specification. Reads the spec, designs architecture, writes code and tests. Delegates to the Forja (Dev) agent.
Pre-release verification checklist. Validates features, tests, docs, security, and quality gates before shipping. Delegates to the Centinela (QA) agent.
Deep security audit covering OWASP Top 10, authentication, authorization, data protection, dependency vulnerabilities, and secrets scanning. Delegates to the Centinela (QA) agent.
Initialize uc-taskmanager for the current project. Creates works/ directory and configures Bash permissions in .claude/settings.local.json. Use when the user says "uctm init", "initialize uctm", "uctm 초기화", or "초기화".
Triggers the WORK-PIPELINE when a user request starts with a [] tag (e.g., [new-feature], [bugfix], [WORK start]). Use this skill whenever you detect a [] tag at the beginning of a user message.