xsyetopz

apply-settings-profile

Preview and apply the dotclaude settings profile to a Claude Code settings file (fast mode off; Opus 5.5, Fable 5.1, and Haiku 4.5 with the Sonnet alias mapped to Opus; built-in git instructions replaced; secret-file read denies; an xhigh effort cap; subagent and workflow bounds), with an optional managed-settings drop-in the user installs with admin rights, and optionally add a marked dotclaude section to the global CLAUDE.md. Run when the user types /dotclaude:apply-settings-profile or asks to apply, update, or check the dotclaude settings.

setup-integrations

Check, install, and configure dotclaude's optional integrations (CodeGraph code-graph MCP, Headroom context compression, and the OpenAI Codex CLI with dotclaude's worker and review profiles), or change their configuration on request. Use when the user asks to set up, install, check, repair, or reconfigure CodeGraph, Headroom, or Codex, or when a dotclaude agent reports one of them missing.

review-code-changes

Review the current uncommitted changes, or a given git range or paths, with the dotclaude code-reviewer agent in a fresh, read-only context, and report findings tied to concrete failure scenarios. Run when the user types /dotclaude:review-code-changes.

codex-fanout

Plan and run a batch of bounded tasks on parallel OpenAI Codex GPT-6 Luna workers (the codex-worker agent) within the user's ChatGPT plan quota, with Claude as orchestrator, reviewer, and committer. Use when the user wants Codex to do a large amount of mechanical or well-specified work (a port, a migration, fixing many failing tests or type errors), or asks to fan work out to Codex or Luna.

drive-web-browser

Drive a real browser with agent-browser CLI or CloakBrowser (antibot) to open pages, click, type, fill forms, take screenshots, and read the rendered page. Use it whenever a task needs to see or operate a running web app or a JavaScript-rendered page. CloakBrowser is recommended for sites with antibot protection as it prevents CAPTCHAs from appearing.

write-session-handoff

Write a handoff note that lets a fresh Claude Code session continue the current task without this conversation, covering the goal, verified state, decisions and rejected approaches, open items, and hard-to-rebuild details. Use it whenever the user wants to hand off, wrap up for a new session, start fresh, save progress before /clear or /compact, pause work to resume later, or asks "what would a new session need to know", even when they do not say "handoff".

blind-spots

Infer what the user is trying to accomplish and tell them what they are not considering, for work where they know part of their goal but expect unknown unknowns. Use when the user names /dotclaude:blind-spots anywhere in a message, or asks what they are missing or not considering.

challenge

Discuss and challenge an idea, plan, claim, or decision instead of agreeing with it, stress-testing its assumptions, failure modes, and alternatives. Use when the user names /dotclaude:challenge anywhere in a message, or asks you to challenge, stress-test, or argue against an idea or plan.

fresh-eyes

Re-review a newly written document, report, or change with fresh eyes for errors, omissions, and weak or unsupported data, using a reviewer that has not seen the authoring reasoning, then fix everything that holds up. Run when the user types /dotclaude:fresh-eyes.

lessons-learned

Post-mortem of the current session, covering what worked, what did not, the systemic causes, and concrete changes (CLAUDE.md lines, skills, hooks, tests, docs) that would prevent the problems next time. Use when the user names /dotclaude:lessons-learned anywhere in a message, or asks for a post-mortem or retrospective of the session.

polish

Review the current change the way a senior perfectionist developer would in code review, list everything they would reject, and fix it. Run when the user types /dotclaude:polish, typically after a feature is built.

recap

Say where the session stands and what it is doing, auditing the whole conversation and correcting anything said earlier that no longer holds. Use when the user names /dotclaude:recap anywhere in a message or asks where things stand, typically right after a compaction or a long stretch of work.

troubleshoot

Switch to troubleshooter mode for the current failure, debugging by measurement and signal tracing instead of guessed fixes. Run when the user types /dotclaude:troubleshoot, typically after a first fix attempt failed.