القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Review implementation against a spec using git diffs to catch mismatches, missing work, and bugs. Supports iterative review+fix with --fix flag and parallel multi-angle review. Use after implementing a feature to verify spec coverage.
Dual-engine spec review — Claude and Codex review the same change in parallel, then a Workflow loops fixes until BOTH engines are MEDIUM-clean. Use when a spec is high-stakes and you want two different models to cross-check for blind spots before implementation. Requires the openai-codex plugin for the Codex engine.
Review a spec, proposal, or design before implementation to catch gaps, risks, and ambiguities. Runs multi-angle parallel review by default; scans codebase for context first. Use --fix for iterative review+fix loop (agent escalates design-judgment issues to you), --angles to narrow the angle set.
Frame a feature, bug, or design question before building: scout the codebase, surface assumptions or interview, compare options, and converge on an explicit decision. Use when an idea needs sharpening before a spec or plan exists. Read-only — never implements.
Synthesize git activity across multiple projects over a time window into themed recall notes. Clusters commits into themes (features, fixes, refactors, infra, learning surface, tickets, side quests), auto-hides empty sections, and surfaces work that PM tools don't track. Use when the user asks 'what did I do last week', wants a multi-project activity summary, or needs to recall their development history.
Merge git branches with auto-generated Conventional Commits messages. Use when merging branches, finishing feature work, or creating merge commits.
| name | reviewer:init |
| description | 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. |
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
$init --from-history
openspec/config.yaml if present, else .claude/reviewer/rules.yaml.
If falling back to the portable target, confirmation of that target happens in the main
conversation (via AskUserQuestion) before dispatch — not inside the agent.--from-history: skip the static template — read the review findings history
(openspec/reviews/history.jsonl, else .claude/reviewer/history.jsonl), cluster
findings recurring across ≥2 changes into candidate rules, confirm each with the user
(AskUserQuestion, multiSelect), and pass only confirmed rules to the agent as the template.
Clustering and confirmation happen in the main conversation, NOT in the agent.
The same pass flags existing rules for retirement — candidates are rules whose finding
class never appears in history or that are superseded by a new candidate (never rules
that went quiet after injection: that silence means they work). Removals get a separate
AskUserQuestion and are applied with Edit in the main conversation; the injection agent
stays append-only.Use the companion init-reviewer.md in this directory as the agent prompt. The agent will cd to the git root automatically. Provide it with: