Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From reviewer
Inject reviewer-aligned rules into openspec/config.yaml so generated specs pass review on first attempt. Use to reduce review round-trips after /opsx:ff or spectra-propose.
How this skill is triggered — by the user, by Claude, or both
Slash command
/reviewer:initThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Inject reviewer rules into your project's `openspec/config.yaml` so that specs generated by OpenSpec tooling satisfy the reviewer's criteria.
Inject reviewer rules into your project's openspec/config.yaml so that specs generated by OpenSpec tooling satisfy the reviewer's criteria.
$init
$init --dry-run
openspec/config.yaml exists in the working directoryUse the companion init-reviewer.md in this directory as the agent prompt. The agent will cd to the git root automatically. Provide it with:
npx claudepluginhub shdennlin/agent-plugins --plugin reviewerSets up DeepWork Reviews by creating or updating .deepreview YAML files for automated code review rules. Guides optimal placement, rule combination to minimize overhead, testing, and summaries.
Walks through a structured interview to customize the review molecule, producing a review-standards.md configuration document for atom loading, severity, report format, scope, insight capture, and health logging.
Reviews code implementation against specification: checks compliance with requirements, identifies deviations, reports score, triggers evolution if needed. Use after implementation or before merging.