Receber por email
← Voltar para o catálogo

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. Delegates to the Forja (Dev) agent.

3.1kestrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add davepoon/buildwithclaude

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/review-findings/svg)](https://www.skillteca.com.br/skills/review-findings)

Skills relacionadas

Ver todas de Marketing →

Alerta por categoria

Receba novas skills de Marketing toda segunda

1 email curto, só com as skills novas de Marketing. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

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

  1. Runs the SIGN IN checklist
  2. Reads the review report and understands each finding's root cause
  3. Plans fix order: Critical first, then Warnings
  4. Implements fixes with updated tests for each finding
  5. Scans for dead code after all fixes
  6. Runs Implementation Complete and Pre-Delivery checklists (TIME OUT)
  7. Verifies every Critical finding addressed, every Warning addressed or deferred with justification
  8. 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
Compartilhar X LinkedIn