strict
The strict slash command enforces disciplined governance practices for a single task by requiring implementation contracts before making extensive edits, running drift detection after edit phases, limiting broad system scans to justified cases, and maintaining concise tool output. Use this when working on critical codebases where unintended changes could cause problems or when you need explicit verification steps before proceeding with substantial modifications.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/0xhimanshu/governor/HEAD/commands/strict.md -o ~/.claude/commands/strict.mdstrict.md
# Governor Strict Mode For the current task, use stricter governance: - require an implementation contract before broad edits - run drift guard after edit phases - avoid broad scans unless justified - keep tool output compact - stop and report when requirements are ambiguous Strict mode is task-scoped. Do not assume it remains enabled for future unrelated tasks unless the user says so.
Audit recurring context files and suggest usage-limit optimizations.
Explain or summarize Governor vs Caveman performance benchmark results.
Automatically compress CLAUDE.md or other memory files with protected-span safety. One-command token savings.
Temporarily ask Governor to avoid compacting tool output for the next diagnostic step.
Check current changes against the latest approved implementation contract.
Install Governor compact-mode rule files into a project for Codex, Gemini, Cursor, Windsurf, or Cline.
Disable Governor compact response mode while keeping telemetry/tool hooks available.
Enable Governor compact professional mode for all prompts in this Claude Code session.