Review Findings Agent Skill
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
one command, takes just this skill from the repositorynpx skills add https://github.com/davepoon/buildwithclaude --skill review-findingsThe instruction itself
8 sections, as written by the authorReview 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
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
Other skills for the same job
different authors, same section of the catalogue
You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, C
Write idiomatic Ruby code with metaprogramming, Rails patterns, and performance optimization. Specializes in Ruby on Rails, gem development, and testing frameworks. Use PROACTIVELY for Ruby refactoring, optimization, or complex Ruby features.
Use when working with tdd workflows tdd refactor
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with truth-score verification.
Prepares codebases for security review using Trail of Bits' checklist. Helps set review goals, runs static analysis tools, increases test coverage, removes dead code, ensures accessibility, and generates documentation (flowcharts, user stories, inline comments).
Refactor high-complexity React components in Dify frontend. Use when `pnpm analyze-component --json` shows complexity > 50 or lineCount > 300, when the user asks for code splitting, hook extraction, or complexity reduction, or when `pnpm analyze-component` warns to refactor before testing; avoid for simple/well-structured components, third-party wrappers, or when the user explicitly wants testing without refactoring.
Write modern C# code with advanced features like records, pattern matching, and async/await. Optimizes .NET applications, implements enterprise patterns, and ensures comprehensive testing. Use PROACTIVELY for C# refactoring, performance optimization, or complex .NET solutions.
How to use it
Take davepoon/review-findings from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.