review
/review
A second opinion before committing. Checks alignment between intent and execution, detects drift, and decides: continue, adjust, or salvage.
Part of the Intent → Execution → Review loop at every scale — from a single commit to a multi-week project. Review closes the loop.
When to Use
Invoke /review when: before committing, at natural pause points, something feels off, scope seems to have grown, or before PRs.
Do not use when: You're in deep flow and making progress. Review at natural breaks, not arbitrary intervals.
Review Lenses
Default to the core workflow review in this file. When the artifact being reviewed needs a sharper domain lens, load the matching supporting reference:
- Code, PRs, technical plans, or implementation work: references/code.md
- Prose, documentation, essays, prompts, or release notes: references/writing.md
- Tutorials, explanations, onboarding, or teaching behavior: references/learning.md
More from open-horizon-labs/skills
dissent
Devil's advocate. Seek contrary evidence before locking in. Use when about to make a significant decision, when confidence is high but stakes are higher, or when the team is converging too quickly.
90ship
Deliver code to users. Optimize the path from merged code to working install. Use when execution is complete and you need to get changes into users' hands.
82problem-space
Map what we're optimizing and what constraints we treat as real. Use before jumping to solutions, when hitting repeated blockers, or when patches keep accumulating.
80execute
Do the work. Pre-flight, build, detect drift, salvage if needed. Use when you have a clear aim and are ready to implement.
79problem-statement
Define the framing of a problem. Change the statement, change the solution space. Use when starting work, when solutions feel wrong, or when you suspect an X-Y problem.
78solution-space
Explore candidate solutions before committing. Use when you have a problem statement and need to evaluate approaches - band-aid, optimize, reframe, or redesign.
76