Receber por email
← Voltar para o catálogo

code-review-pipeline

Revisão de código multidimensional abrangendo correção, segurança, desempenho e manutenibilidade, com relatórios condicionados por confiança e ciclos de remediação.

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

Overview

Multi-dimensional code review methodology adapted from the Everything Claude Code project. Reviews across 4 dimensions with confidence-gated issue reporting and automated remediation loops.

Review Dimensions

Dimension 1: Correctness

  • Logic errors and off-by-one mistakes
  • Edge case handling (null, undefined, empty, boundary)
  • Type safety (no implicit any, proper narrowing)
  • Error handling completeness
  • Floating promise detection
  • Race condition analysis

Dimension 2: Security

  • Injection vectors (SQL, XSS, command, template)
  • Authentication and authorization gaps
  • Data exposure (PII, credentials, internal state)
  • Dependency vulnerabilities (known CVEs)
  • Input validation completeness

Dimension 3: Performance

  • Algorithmic complexity (O(n^2) detection)
  • Memory leaks (event listeners, closures, caches)
  • Unnecessary allocations in hot paths
  • Database query optimization (N+1, missing indexes)
  • Bundle size impact

Dimension 4: Maintainability

  • Naming clarity and consistency
  • Documentation completeness (JSDoc, inline comments)
  • Test coverage adequacy
  • Coupling analysis (afferent/efferent)
  • File organization compliance

Confidence Gating

  • Score each issue 0-100 on confidence
  • Only report issues >= 80% confidence
  • Prevents false positive noise
  • Higher confidence for clear patterns, lower for heuristic matches

Remediation Loop

  • Prioritize: critical > high > medium > low
  • Apply fixes via refactor-cleaner agent
  • Re-review after remediation
  • Maximum 2 remediation cycles
  • Exit when no critical/high issues remain

When to Use

  • Post-implementation review
  • Pre-merge PR review
  • Security audit
  • Technical debt assessment

Agents Used

  • code-reviewer (primary)
  • refactor-cleaner (remediation)
Compartilhar X LinkedIn