Menu
Review Conventions
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Orchestrate parallel implementation of multiple beads across cmux panes in dependency-aware waves. Use when implementing a whole feature area, dispatching multiple beads at once, or running parallel cld -b sessions. MUST USE when user says "wave", "parallel beads", "implement all beads for X", "start the beads", or references implementing more than 2 beads at once. Also triggers on "cmux dispatch", "multi-bead", "wave orchestrator".
Audit a repo for ADR hoist debt and pre-trinity packages. Triggers on: adr gap, hoist debt, adr audit, pre-trinity packages, architecture drift.
Troubleshoot beads Dolt failures: `bd dolt` push/pull errors, merge conflicts, embedded/shared-server mode problems, remote auth issues, local DB recovery, re-clone, reflog restore, broken `.beads` Dolt config, and brew-services Dolt lifecycle. Use whenever beads sync or Dolt infrastructure is failing — symptoms like "beads do not sync", "cannot push issues", "no common ancestor", "not supported in embedded mode", "Dolt server unreachable", or "lost local database". Read the beads changelog first. Do not use for normal beads tracking (`bd create/ready/close`), standalone Dolt databases, or regular git push/pull.
Create and review agents (subagents). Use when creating specialized AI assistants, reviewing/auditing existing agents, deciding between agent vs skill vs command, or asking about agent best practices, multi-agent pipelines, and model selection. MUST BE USED when the user says "create agent", "new subagent", "review agent", "audit agent", "agent vs skill", or asks about multi-agent architecture.
Query per-bead token cost metrics from the local agent metrics database. Shows cost table, impl:review ratios, most expensive beads, cost trend over time. Triggers on: bead metrics, token cost report, bead costs, /bead-metrics.
Structured 4-stage retrospective for completed beads: Requirements vs Strategy, Strategy vs Execution, Iteration Review, Workflow Audit. Creates Trap/Pattern/Decision artifacts. Use when debriefing a bead, capturing session learnings, or running a compound retrospective.
| name | review-conventions |
| description | Review Conventions |
| requires_standards | ["english-only"] |
Scan this project for undocumented coding conventions and propose new standards.
Use the convention-reviewer agent from agents/agentos-lite/ to:
<global-standards-dir>/index.yml<project-standards-dir>/index.yml (project, if it exists)Optional input arguments describing the scan scope.
If no scope specified, analyze the entire project. Examples:
review-conventions - Full project scanreview-conventions src/ - Only src directoryreview-conventions --recent - Only files changed in last 20 commitsFor each proposed convention, provide:
This command does NOT create standards automatically. After review:
review-conventions src/adapters/
Would analyze adapter classes and propose standards for common patterns found.