Trigger when the user asks to add a changeset or document a change: "add a changeset", "document this change", "what changed here". Extracts the consumer-facing meaning of a diff: classifies consumerimpact (behavior-change, new-capability, internal-only) and semverimpact (major, minor, patch, none) per…
Trigger when the user asks to commit code or write a commit message: "commit this", "write a commit message", "commit the staged changes". Reads the staged git diff and produces a conventional commit message explaining why the change was made, not what changed — the diff already shows what changed.
Trigger when the user has an already-drafted review or reply and wants it posted: "post this review", "reply to this comment", "mark this thread resolved", "submit my review comments". Takes drafted content — from the built-in code-review skill's findings, from courier/receive-feedback's response plan, or typed…
Trigger when the user asks to open a PR or write a PR description: "open a PR", "create a pull request", "write the PR description". Given a diff, a linked spec, and a linked requirement, produces a PR title and body a reviewer with zero context can act on, then opens the PR via gh pr create after user confirmation.
Trigger when the user asks to process or triage incoming review feedback: "address the feedback", "respond to review comments", "what do these comments mean", "triage this review". Assembles a review package — diff summary, linked spec, test results, open questions — so the author has full context to respond without…
Trigger when the user asks to cut a release or summarize what's in one: "cut a release", "what's in this release", "generate release notes". Aggregates changeset@2 entries since the last release into a release-artifact@2: filters consumerimpact: internal-only entries, computes the version as max(semverimpact) across…
Trigger when the user asks to check an existing plugin for conformance: "audit this plugin", "check plugin conformance", "does this plugin follow the ecosystem rules?". Given a plugin directory path, checks plugin.json required fields, subagent file presence for every declared agent, YAML frontmatter completeness…
Trigger when the user wants to design a new inter-agent artifact schema: "design a schema for X", "add a new schema to shared/schemas", "what should this handoff look like?". Given a description of what the artifact represents, who produces it, and who consumes it, produces a JSON Schema (draft 2020-12) following…
Trigger when the user asks to build a new plugin from scratch: "build a new plugin", "create a plugin for X", "scaffold a plugin directory". Given a plugin ID and a description of what it should do, generates a complete, installable plugin directory — plugin.json, skills/ /SKILL.md, one stub agent file per declared…
Trigger when the user wants one new agent added to an existing plugin: "write an agent for X", "add a subagent to this plugin", "create a subagent for this task". Given an existing plugin's directory, a task description, and a model/effort tier, generates a single conformant agent file at plugins/ /agents/ .md using…
Trigger when the user asks to spec a UI component: "spec this component", "draft a component spec", "write a spec for this design", "audit this component spec", "is this component spec ready?", "gate this component spec". Given a requirement@1 or free-text design intent, produces a spec@1 covering props, variants…
Trigger this skill when the user says "write a plan for X", "how do we implement this spec", "break this down into tasks", "what are the implementation steps", "create an implementation plan", or "plan this out". Also activate when a spec (spec@1) exists and the user is ready to move to implementation but hasn't…
Trigger this skill when the user asks to perform a bug hunt, code audit, find bugs, security audit, defect scan, vulnerability scan, code review for bugs, or asks "what's wrong with this code." Activate for any codebase language — Rust, TypeScript, or JavaScript. 5-phase pipeline: (1) recon builds a verified module…
Trigger when ranger has returned a finding-report@1 and the confirmed defect class needs a structural fix — a change to the architecture, type system, interface boundary, or abstraction layer — rather than patches to individual instances. Given a finding-report@1, produces a spec@1 for the structural change that makes…
Trigger when the user asks to review a spec's quality: "review this spec", "is this spec complete?", "audit this spec". Given a spec@1, adversarially reviews it for untestable criteria, ambiguous language, missing error cases, scope overlap with other specs, and incomplete sections. Returns a structured issue list…
Trigger when implementer reports that a spec criterion contradicts what the system actually does: a speccontradiction status from smith. Given a specfilepath, the criterionid of the affected acceptance criterion, and a contradiction report (what the spec says vs. what the system actually does), revises the affected…
Trigger when the user asks to write or draft a spec: "spec this out", "draft a spec", "write a spec for this requirement". Given a requirement@1 and optionally a research-report@1, produces a spec@1 draft with purpose, scope, nongoals, apisurface (if applicable), and acceptance criteria. Every criterion is a testable…
Trigger when a spec@1 needs a definitive pass/fail judgment before it enters planning: "gate this spec", "is this spec ready?", "check this spec before we plan it". Default disposition is fail — the spec must earn a pass. Passes only if every acceptance criterion is testable with no vague language, no TBDs remain…
Trigger when the user asks whether implemented code still matches its spec, weeks or months after implementation: "check spec drift", "does the code still match this spec?", "has this spec drifted?". Given a spec@1 (via specfilepath) and a workspace root, reads the spec from disk and the implementation from the…
Trigger when the user asks whether a spec matches its source: "is this grounded?", "does this spec match the requirement?", "check this spec against the requirement". Given a draft spec@1 plus the originating requirement@1 and optional research-report@1, checks whether each acceptance criterion is grounded in the…
Trigger this skill when the user says "verify this", "check this spec", "check this plan", "check this requirement", "check this PR", "is this done?", "review this for completeness", "does this meet the criteria?", "gate this", or "quality check" — also before stage transitions: starting implementation from a spec…
Activate when the user says "implement this", "execute the plan", "write the code", "build this feature", "generate tests for X", "write tests for this spec", "refactor this without changing behavior", or "explain what this code does" — also when handed a plan@1 to execute, or a spec@1 exists but no plan. Every task…
Activate when the user says "I need to understand X before deciding", "is there a way to do Y", "what are the options for Z", "research this", "investigate this", "what does the codebase already do for X", "prior art on Y", or "what are the risks of approach Z" — also when the approach for a spec or plan is unclear…
Trigger when the user asks about overall backlog health: "what's in the backlog", "audit the backlog", "what requirements are missing coverage". Cross-references all open requirement@1 objects against existing specs and implementation files. Returns per-requirement status (covered, partial, missing, duplicate) with…