Skip to content

a5c-ai/babysitter / library/methodologies/everything-claude-code/skills/code-review-pipeline

code-review-pipeline

Verified

Multi-dimensional code review across correctness, security, performance, and maintainability with confidence-gated reporting and remediation loops.

FileKindSize
README.mdmarkdown248 B
SKILL.mdskill md2.0 KB
---
name: code-review-pipeline
description: Multi-dimensional code review across correctness, security, performance, and maintainability with confidence-gated reporting and remediation loops.
allowed-tools: Read, Bash, Grep, Glob
graph:
  domains: [domain:software-engineering]
  skillAreas: [skill-area:agentic-loops, skill-area:orchestration-loop]
  workflows: [workflow:feature-development]
  topics: [topic:developer-experience]
  roles: [role:tech-lead, role:backend-engineer]
---

- 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)
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall