Agent Skills
› davepoon/buildwithclaude
› review-findings
review-findings
GitHub用于处理QA代码审查发现。通过Forja代理修复严重和警告问题，更新测试，生成修复报告并准备重新验证。
Trigger Scenarios
收到Centinela QA的代码审查报告后
需要解决审查报告中的发现项时
在重新验证前修复关键和警告问题
Install
npx skills add davepoon/buildwithclaude --skill review-findings -g -y
SKILL.md
Frontmatter
{
"name": "review-findings",
"category": "workflow-orchestration",
"description": "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."
}
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
- 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
Version History
- 502fc01 Current 2026-07-05 15:01
