code-review skill
Structured code quality assessment with Conventional Comments format, scaled review depth, and soft-gating verdicts preserving user autonomy.
A100/100content scan
Is the code-review skill safe?
Clean: nothing in its files matched our rules. We read 2 files in the folder on 2026-09-28.
No findings.
Install the code-review skill
A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.
git clone --depth 1 https://github.com/a5c-ai/babysitter.git /tmp/babysitter mkdir -p ~/.claude/skills cp -r /tmp/babysitter/library/methodologies/rpikit/skills/code-review ~/.claude/skills/code-review
available in every project
In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub
The instructions your agent would load
SKILL.md as published, without the frontmatter. Read it on GitHub
- When reviewing code changes before merge
- As part of the /review-code command
Process
- Identify modified files via git
- Assess change magnitude for review depth
- Execute 9-step review: context, correctness, design, testing, security flags, operations, maintainability
- Synthesize findings in standardized report
- 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
More skills from a5c-ai/babysitter
- Aadversarial-reviewFresh adversarial code review with binary PASS/FAIL verdicts, evidence citations, and anchoring bias prevention via fresh reviewer spawning.
- Aagent-boosterWASM-based instant code transforms for simple tasks, achieving 352x speedup over LLM inference with zero cost.
- Aagent-coordinationCoordinate Crew (persistent) and Polecat (transient) agents using Gas Town's hook-based work distribution and GUPP principle.
- Aagent-dispatch
- Aanti-driftHierarchical coordination and drift detection with frequent checkpoints, shared memory coherence validation, role specialization enforcement, and short task cycles.
- Aarchitecture-design
- Aarchitecture-patternsSystem and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.
- Aassimilate-popular-workflowsThis skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable processes, babysitter plugins, and reusable procedural insights. Searches GitHub for SKILL.md files, classifies repos by archetype, and maintains structured research under docs/reference-repos/.
- Aaudit-trail
- AbabysitOrchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
- Ababysit-babysitter-issuesThis skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.
- Abehavior-contractBug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.