Receber por email
← Voltar para o catálogo

code-review

Avaliação estruturada da qualidade do código com formato Conventional Comments, profundidade de revisão escalonada e vereditos de soft-gating que preservam a autonomia do usuário.

1.4kestrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add a5c-ai/babysitter

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/code-review-a5c-ai/svg)](https://www.skillteca.com.br/skills/code-review-a5c-ai)

Skills relacionadas

Ver todas de Automação →

Alerta por categoria

Receba novas skills de Automação toda segunda

1 email curto, só com as skills novas de Automação. 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

Code Review

Overview

Assess code quality, design, correctness, and maintainability through a structured 9-step review workflow. Uses Conventional Comments format with file-specific references.

When to Use

  • After implementation phase completes
  • When reviewing code changes before merge
  • As part of the /review-code command

Process

  1. Identify modified files via git
  2. Assess change magnitude for review depth
  3. Execute 9-step review: context, correctness, design, testing, security flags, operations, maintainability
  4. Synthesize findings in standardized report
  5. Deliver verdict with rationale

Review Depth Scaling

  • Under 200 lines: full detail review
  • 200-1000 lines: focused review on critical areas
  • Over 1000 lines: architectural-level review only

Verdicts

  • APPROVE: Ready for security review
  • APPROVE WITH NITS: Non-blocking suggestions only
  • REQUEST CHANGES: Blocking issues exist (user may override)

Key Rules

  • Provide specific file paths and line numbers
  • Include at least one positive comment per review
  • Use Conventional Comments format with decorations
  • Explain reasoning, not just observations
  • Limit critical issues to top 5 per category
  • Reviews are soft gates preserving user autonomy

Tool Use

Invoke via babysitter process: methodologies/rpikit/rpikit-review

Compartilhar X LinkedIn