dso

Create a git commit with mandatory test, format, review gates.

Diagnose and fix all outstanding bugs, test failures, lint errors, and infrastructure issues.

Invoke the `/dso:end-session` skill, passing through any arguments: $ARGUMENTS

Review current code diff using a code-reviewer sub-agent.

Evaluates implementation proposals against 5 quality dimensions and returns ADR-style selection rationale or counter-proposal

Evaluates probabilistic bloat candidates from /dso:remediate, classifying each as CONFIRM (likely bloat), DISMISS (false positive), or NEEDS_HUMAN (ambiguous). Enforces asymmetric error policy — defaults to DISMISS when uncertain because false CONFIRMs are amplified downstream.

Applies confirmed bloat removals from /dso:remediate Path B (auto-resolve). Treats its output as final — performs dependency checks before each deletion and emits NO_CHANGE with categorized reasons when removal is unsafe.

Structured filter that evaluates red team adversarial findings against the original story map and removes false positives, speculative concerns, and low-signal noise.

LLM behavioral debugger agent. Diagnoses divergent, unpredictable, or failing behavior in other LLMs and agents using a 16-point failure taxonomy, 5 RCA probes, and an iterative hypothesis-experiment-analyze loop. Emits a structured RESULT schema compatible with /dso:fix-bug.

Use when the user wants to set up architecture rules, code standards, guardrails, fitness functions, lint configs, or enforce project conventions after onboarding has run. Reads .claude/project-understanding.md (written by /dso:onboarding) and uses Socratic dialogue to surface enforcement preferences and anti-pattern risks, then generates targeted enforcement scaffolding (CI checks, lint rules, fitness functions, ADRs) without re-running project detection. Trigger phrases include 'set up code standards', 'add architecture rules', 'enforce conventions', 'add guardrails', 'lock in patterns', 'set up linting', 'add fitness functions'.

Use when starting a new feature or epic — turns a feature idea into a defined, ticket-ready epic through Socratic dialogue with the user. Designs technical approaches, breaks features into milestones, drafts ticket descriptions and success criteria, and writes the epic to the ticket tracker. Trigger phrases include 'plan a feature', 'spec out a feature', 'break down work', 'create user stories', 'start a new epic', 'turn this idea into tickets', 'roadmap a feature'.

Use when an agent or user needs to file a bug, report an issue, create a defect ticket, or capture a sub-agent blocker. Creates well-formatted, evidence-based bug tickets by collecting reproduction steps, expected vs. actual behavior, environment details, and logs, then writing the ticket via the ticket CLI using the shared bug report template. Trigger phrases include 'file a bug', 'report an issue', 'create a bug', 'open a ticket', 'log a defect', 'submit a bug report'.

Use when reviewing proposed designs (code, wireframes, screenshots) against an established .claude/design-notes.md, or when enforcing design system compliance before merging UI changes. Checks color tokens, typography, spacing, component usage, layout, and accessibility against the project's design notes and produces a report card with critical violations, UX/accessibility risks, alignment wins, and optional refined code. Trigger phrases include 'design review', 'style guide check', 'visual consistency', 'component library compliance', 'design system check', 'review this UI', 'check design tokens'.

Use when the user wants to dry-run a DSO skill, simulate its execution, or preview its planned changes without executing them. Wraps any /dso:* skill invocation with override rules that block all mutating operations (ticket writes, file edits, git commits) while still running read-only steps; emits [DRYRUN] preview blocks for each blocked mutation and a final summary of what would have changed. Trigger phrases include 'dry run', 'simulate', 'what-if', 'test run', 'no-op', 'preview without changes', 'show me what would happen'.

14 hooks across 6 events