Skills and Slash Commands

Skills and slash commands turn repeated work into a named workflow. Use them after a pattern is stable enough that humans would otherwise paste the same instructions again and again.

Slash Commands

Slash commands are best for short, direct workflows:

• Run a release checklist.
• Generate a focused review prompt.
• Start a documented debugging routine.
• Prepare a handoff summary.

Example command body:

Inspect changed files, identify risky behavior changes, run the focused test if available, and
return findings first with file references.

Skills

Skills are better for multi-step workflows with reference material, scripts, or templates. A useful skill explains when to use it, what files to read, and what output to produce.

Good skill contents:

• Trigger conditions.
• Required repository conventions.
• Scripts or templates to reuse.
• Verification requirements.
• Known failure modes.

Frontmatter Discipline

If a workflow needs a specific reasoning level or model behavior, encode that in the command or skill metadata where supported. Keep the body operational:

---
description: Review handbook route changes for locale regressions.
---

Check route helpers, sitemap generation, localized links, and E2E coverage.

Governance

Review commands and skills like production code. Remove stale ones, merge duplicates, and keep high-risk automation visible to the team.