beo-review
Review atomic work beads against requirements and ticket scope. Only this skill can close accepted work.
Install
mkdir -p .claude/skills/beo-review && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11799" && unzip -o skill.zip -d .claude/skills/beo-review && rm skill.zipInstalls to .claude/skills/beo-review
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Review one executed atomic BEO bead against its self-contained description, TICKET.yaml scope, evidence, verification, and done criteria. Emits one route; only this skill may close accepted work.Key capabilities
- →Review executed BEO beads against self-contained descriptions
- →Verify implementation against TICKET.json scope
- →Check if done criteria are covered by evidence
- →Confirm verification results support done criteria
- →Audit changed files against approved scope and generated outputs
- →Emit exactly one review route based on findings
How it works
The skill performs a fresh read of the bead's context, then applies a rubric to evaluate scope, intent, done criteria, and verification. It audits changed files and emits a single review route based on the findings.
Inputs & outputs
When to use beo-review
- →Verifying bead implementation against scope
- →Checking completion criteria for tasks
- →Closing accepted work items
- →Ensuring worktree isolation compliance
About beo-review
Reviews executed BEO beads by comparing implementation against the self-contained description, TICKET.json, and verification criteria. It enforces strict cross-checks and allows the closing of accepted work.
Review one executed atomic BEO bead against its self-contained description, TICKET.yaml scope, evidence, verification, and done criteria. Emits one route; only this skill may close accepted work.
When not to use it
- →When the task is not reviewing an executed atomic BEO bead
- →When the skill is asked to mutate product files
- →When the skill is asked to close non-accepted work
Limitations
- →May only close accepted work
- →Must not mutate product files
- →Must not grant PASS_EXECUTE
How it compares
This skill provides a strict, rubric-based review process for BEO beads, ensuring all criteria are met and evidence is present before work is accepted, which is more rigorous than a general code review.
Compared to similar skills
beo-review side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| beo-review (this skill) | 0 | 3mo | No flags | Advanced |
| resolve-conflicts | 81 | 10mo | Review | Intermediate |
| claude-automation-recommender | 47 | 4mo | Review | Beginner |
| codex-skill | 12 | 6mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
claude-automation-recommender
anthropics
Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
codex-skill
feiskyer
Use when user asks to leverage codex, gpt-5, or gpt-5.1 to implement something (usually implement a plan or feature designed by Claude). Provides non-interactive automation mode for hands-off task execution without approval prompts.
git-advanced-workflows
wshobson
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
subagent-driven-development
davila7
Use when executing implementation plans with independent tasks in the current session
validate-openapi-specs
epieczko
Validates and registers hook manifest files (YAML) in the Hook Registry for versioned hook management.