All 94 skillsQuality4 of 13
stryx:review
When code or a pull request should be checked before commit or merge.
/stryx:reviewInside its piece: 20 specks, one for each file on its shelf. Its twelve group-mates glow on the open book behind it. The light splits toward orange, the band of Quality.
In numbers
counted 2026-10-12 in the installed set- 17reference files
- 1helper scripts
- 20files in the skill
- 239KB on disk
- 17chapters
- 2agents work by this book
Use it when
in the skill’s own words- When reviewing code or a pull request ("review this", "check my changes", "is this code good", "audit this diff", "review the PR", "deep / full / quick review", "second opinion", "codex review"), after finishing a task or feature and before commit or merge, when reading unfamiliar inherited code, and when a workflow needs a review verdict or JSON receipt
Not for
another skill does it- Acting on review feedback you received→ stryx:review-feedback
- Proving work is done or running the build/test gate→ stryx:verify
- Reviewing plans or specs→ stryx:plan-review
- Diagnosing failures→ stryx:debug
What it covers
Covers six always-on lenses (logic, security, performance, architecture, UI/design, simplicity) plus triggered contracts and history lenses, severity and confidence, verdicts, review depth and parallel Stryx reviewer agents, second opinions, and the reviewer-subagent brief.
On its shelf
20 files, 239 KB- references/17
- SKILL.md1
- evals/1
- scripts/1
Inside the book
17 chapters, by title only- Procedure in short
- Resolve the scope
- Choose the depth
- Review protocol - four steps, no shortcuts
- The lenses
- Severity
- Confidence
- Pragmatic filters
- Verdict and output
- Code Review: <title>
- Verification gates and anti-premature completion
- Multi-agent review and second opinions
- Requesting a review (dispatching a reviewer subagent)
- Receiving feedback (author side)
- Applying fixes
- Scale mappings
- Worked example (quick depth, one IPC change)
Its helpers
2 agents work by this book- stryx:perf-agentWhen an app needs a speed audit, or one named thing must get measurably faster.
- stryx:reviewerWhen changes need a code review with a verdict before commit or merge.
Works with
the skills it names most- stryx:review-feedback→When someone reviewed the work and their comments must be answered and fixed.
- stryx:execute→When a written plan must be carried out to the end, or you say "keep going until it passes".
- stryx:verify→When Claude is about to say done, fixed or ready to commit: fresh proof comes first.
- stryx:orchestrate→When a job could use more than one agent: how to split it, staff it and merge the results.
- stryx:debug→Something is broken: a bug, an error, a crash, a failing test or wrong data.
- stryx:mneme→When the Mneme memory server is connected and you ask where code is or what a change breaks.
Claude loads it by itself when the moment comes; by hand, type the line at the top. It comes with the whole set: Installs all 94 skills, 32 agents and the brain program as one set. The skill’s own text is private source and is not shown here.