OpenParable
Skip to content
← Back to skills

Code Review Patterns

Testing & Quality
code-review-patterns

Code Review Patterns is an Agent Skill for testing & quality published in the a5c-ai/babysitter repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Multi-dimensional code assessment across security, quality, performance, and maintainability with confidence-gated reporting (>=80%) and Router Contract generation.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/a5c-ai/babysitter/blob/HEAD/library/methodologies/cc10x/skills/code-review-patterns/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/code-review-patterns, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

  • Injection vulnerabilities (SQL, XSS, command)
  • Authentication and authorization patterns
  • Secrets handling (no hardcoded credentials)
  • Input validation and sanitization

Quality (weight: 25%)

  • Naming conventions and consistency
  • Code structure (SRP, cohesion, coupling)
  • Error handling completeness
  • Type safety (no any escapes)

Performance (weight: 20%)

  • Algorithmic complexity (flag O(n^2) or worse)
  • Resource and memory leaks
  • Database query efficiency (N+1)
  • Caching opportunities

Maintainability (weight: 25%)

  • Documentation (JSDoc/TSDoc for public APIs)
  • Test coverage adequacy
  • Readability (function length, nesting depth)
  • Tech debt markers (TODO, FIXME)

Confidence Gating

  • Only report issues with confidence >= 80%
  • Empty catch blocks are always critical (100% confidence)
  • Classify: critical, high, medium, low
  • Include actionable remediation for each issue

Router Contract

Every review must produce: STATUS, BLOCKING, REQUIRES_REMEDIATION, issue counts.

When to Use

  • Code review step in BUILD workflow
  • Fix review in DEBUG workflow
  • Full REVIEW workflow

Agents Used

  • code-reviewer (primary consumer)
  • silent-failure-hunter (error handling dimension)