review-findings

Parse QA review reports and apply fixes by severity through verification loops.

3|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/ArtemioPadilla/agent-triforce --skill review-findings-artemiopadilla
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: review-findings
Source: https://github.com/ArtemioPadilla/agent-triforce/tree/main/.claude/skills/review-findings
Command: npx skills add https://github.com/ArtemioPadilla/agent-triforce --skill review-findings-artemiopadilla

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps QA teams systematically address findings from code reviews by surfacing, classifying, assigning, and tracking fixes, ensuring issues are resolved and re-verified before release.

Core Features & Use Cases

  • Defect triage and classification: parse the review report, categorize findings by severity (Critical/ Major/ Medium/ Minor) and status, and assign ownership.
  • Lifecycle tracking: streamlines the Open โ†’ Assigned โ†’ Implemented โ†’ Verified โ†’ Closed workflow across Centinela, Forja, and Centinela cycles.
  • Documentation and verification: ensures tests pass, updates TECH_DEBT.md for remaining minor findings, and generates a re-verification checklist.
  • Use Case: When a QA review identifies multiple issues across a feature, this skill coordinates prioritization, fixes, tests, and re-verification steps.

Quick Start

Begin by loading the most recent QA review from docs/reviews and initiating the Open findings fix workflow.

Frequently Asked Questions about review-findings

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix QA findings and re-verify code review defects systematically?โ–ผ

Fix QA findings by parsing the review report, applying the most severe defects first, tracking status through the Centinela and Forja verification loop, and ensuring all Critical and Major issues are Implemented before handoff.

What is the workflow for defect triage and classification from a code review?โ–ผ

Defect triage involves parsing the QA review report, categorizing findings by severity (Critical, Major, Medium, Minor) and status, and assigning ownership to streamline the Open to Closed lifecycle workflow.

How do I track code review findings through the Open to Closed lifecycle?โ–ผ

Track code review findings through the Open, Assigned, Implemented, Verified, and Closed workflow by coordinating handoffs and re-verification across the Centinela, Forja, and Centinela verification cycles.

Where should I document remaining minor findings during QA defect tracking?โ–ผ

Document remaining minor findings during QA defect tracking in TECH_DEBT.md, ensuring tests are updated and passed while generating a re-verification checklist before final handoff.

Do I need a QA review report before starting the defect resolution workflow?โ–ผ

You need a QA review report loaded from docs/reviews to initiate the Open findings fix workflow, which parses identified issues across a feature to coordinate prioritization, fixes, tests, and re-verification steps.

When should I document technical debt instead of immediately fixing a code review finding?โ–ผ

Document technical debt in TECH_DEBT.md for remaining minor findings after ensuring all Critical and Major findings are Implemented, tests are updated, and the re-verification checklist is generated for handoff.