AI Agent Workflow Collection

Conventional Commits message generator from current staged + unstaged changes. Read-only — runs only allowlisted git commands, never commits, never pushes, never adds AI co-author trailers. Output is plain text the user pastes. Triggers: "suggest a commit", "commit message", "commit msg", "write a commit", "gen conventional commit", "what should this commit say", "/commit". Classifies type (feat/fix/chore/refactor/docs/test/perf); subject under 50 chars; body only when "why" isn't obvious from the diff.

Opt-in setup for auto-journaling capture plumbing. Copies bundled PostToolUse hook scripts into .squad/hooks/ and prints the .claude/settings.json snippet to wire them up. Capture-only — squad behaviour does NOT change until a follow-up release adds distillation + retrieval. Triggers: "enable journaling", "turn on auto-journaling", "set up the work-trail hook", "capture tool calls", "opt in to journal", "/squad:enable-journaling". One-shot setup — no args, no flags.

Socratic plan validation. Grills your plan one question at a time against the project's domain language (CONTEXT.md) and prior decisions (ADRs in docs/adr/), updating both inline as terms resolve. Catches terminology drift, hidden assumptions, and undocumented decisions BEFORE implementation. WRITES to CONTEXT.md and docs/adr/ with per-write confirmation — use --no-write for dry-run. Triggers: "grill my plan", "stress-test this plan", "validate this approach", "is this consistent with our domain", "are there decisions missing", "before I implement", "challenge my assumptions", "/grillme". Example: "/squad:grillme --deep store user notifications in a separate table". For exploring options BEFORE a plan exists, use /brainstorm. For implementation, use /squad:implement.

Catalog of components (PascalCase files), hooks (useFoo), pages/routes, story files, and token files in the codebase. Use to understand what already exists before adding more, or to audit a design system. Heuristic-based, no AST. Run as node ~/.claude/skills/dragoon/skills/inventory/scripts/inventory.js [root].

Read-only code Q&A. Spawns the code-explorer subagent (Haiku-class) for grep/glob/excerpt and synthesizes a cited answer with file:line citations. Fast. Never writes files, never commits, never runs the squad. Use for "where is X defined", "what calls Y", "how does Z work", "show me the implementation of", "find references to", "explain this code", "locate in the codebase", "trace through", "what files use X", "where does Y happen". Example: "/squad:question where is the rate-limit middleware applied?". For a known failure with stack trace, use /squad:debug instead. For implementing a fix or feature, use /squad:implement.

Multi-agent advisory squad workflow for implementing or reviewing code changes. Two modes — implement (default) runs classify → score risk → select agents → planner → Gate 1 → advisory squad → Gate 2 → implementer → consolidator → verdict; review runs advisory-only on an existing diff/branch/PR/commit. Dispatches named subagents (architect, dba, developer, reviewer, security, qa, tech-lead-planner, tech-lead-consolidator, product-owner); each scores its dimension 0-100 and the consolidator weights them into a rubric scorecard with APPROVED/CHANGESREQUIRED/REJECTED verdict. Triggers: "run the squad", "advisory review", "implement with squad", "code review by specialists", "review this PR", "review my diff", "review my branch", "implement this feature", "build this with the squad", "/squad:implement", "/squad:review". Example: "/squad:implement --normal add OAuth login flow" or "/squad:review --deep main..feature/auth-rewrite". For decision-only (no code yet), use /brainstorm. For plan stress-test, use /squad:grillme.

Use when user invokes /stats or asks about Claude Code usage, token consumption, session history, model distribution, or activity patterns.