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
- yesterday
- Language
- TypeScript
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
review-code
Review code changes for correctness, safety, maintainability, and test coverage.
review-address
Use when the user wants to act on code-review feedback on the current branch — review comments, findings, PR feedback, or a reviewer's punch list. Triggers on phrases like "address the review items", "respond to the review", "fix the review findings", "handle the PR comments", "action the reviewer feedback", or "address each issue in separate commits". Fixes only what the branch introduced, one finding per commit, behind the project's quality gates; anything pre-existing or history-rewriting is surfaced for a decision instead of silently done.
code-review
Review changed code for correctness bugs — logic errors, nil/error handling, concurrency, resource leaks, edge cases, broken invariants. Reports findings first, ordered by severity, then fixes on request. Scoped to correctness, not quality or style cleanups. Use when the user says "code review", "review my changes", "any bugs", "find bugs", or asks whether a change is correct.