Skill

review-findings

Addresses and fixes findings from a QA code review. Reads the review report, fixes critical and warning issues, and prepares for re-verification.

Install

npx claudepluginhub artemiopadilla/agent-triforce

Tool Access

This skill uses the workspace's default tool permissions.

SKILL.md

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

157.6k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

157.6k

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

ecc

150.0k

Stats

Parent Repo Stars3

Parent Repo Forks0

Last CommitMar 1, 2026

Actions

View Source View Plugin View on GitHub View README

Fix the findings from the QA review: $ARGUMENTS

If no specific review is mentioned, look for the most recent review in docs/reviews/.

Follow these steps:

SIGN IN:

Run the SIGN IN checklist from your agent file
Surface any concerns about the findings — complexity, risk, dependencies

⏸️ TIME OUT — Pre-Fix Preparation (READ-DO):

Read the review report in docs/reviews/
Understand each finding's root cause BEFORE writing any fix
Plan the fix order: Critical first, then Warnings
Identify if any fixes could conflict with each other

FIX (using Clean Code principles): 5. For each finding:

Understand root cause (don't just fix the symptom)
Apply appropriate refactoring technique: Extract Method, Rename, Move, Inline, Replace Conditional with Polymorphism
Write or update tests to prevent recurrence (Arrange-Act-Assert)
Verify the fix doesn't introduce new code smells

Scan for dead code after all fixes — apply Boy Scout Rule

⏸️ TIME OUT — Run Implementation Complete + Pre-Delivery Checklists (DO-CONFIRM): 7. Run the Implementation Complete checklist from your agent file 8. Run the Pre-Delivery checklist from your agent file Additionally verify:

Every Critical finding addressed
Every Warning addressed (or explicitly deferred with justification)
No new code smells introduced by the fixes

SIGN OUT: 9. Write a Fix Report using the Fix Report checklist from your agent file 10. Run the SIGN OUT checklist from your agent file