claude-code-guardrails

claude-code-guardrails

Hooks, commands and an output style I use with Claude Code, extracted
from my private config.

- Hooks — run outside the model's judgment: block bulk git add / git commit -a and
  WHERE-less SQL before the Bash call executes, record the session-start commit, snapshot work
  state before context compaction and feed it back in right after, run the project's own formatter
  after edits.
- Commands — a delivery loop (/plan → /implement → /verify → /critical-review →
  /crosscheck) and doc-maintenance commands (/save-learnings-to-docs, /cleanup-docs,
  /refactor-claude-md, /init-local-md).
- Reviewer backend — /critical-review runs an independent, read-only reviewer on the diff
  (Codex CLI, Claude Code CLI, or your own command) through one adapter script, and never shows it
  the task brief.
- Skill — browser-mcp: how to drive chrome-devtools-mcp cheaply and safely (which server for
  what, token-cheap check order, screenshot/emulate pitfalls, secrets, logged-in apps).
- Output style — terse.md: result first, no padding.
- Fleet sync — push commands/skills/styles to your servers over SSH, audit drift with --check.

Quick start (fresh Mac)

You need Claude Code ≥ 2.1, installed and logged in. Homebrew is optional.

1. Command-line tools. Install them if git --version asks for them: xcode-select --install.
   They provide git and python3.
2. The plugin. In Claude Code, run the two commands below, then restart Claude Code:

   - Hooks are active right away.
   - Commands and the skill are namespaced: /guardrails:plan, /guardrails:critical-review,
     guardrails:browser-mcp, ….
3. Check what works here. /guardrails:setup-check prints ✓/✗ per part, with the exact fix for
   each gap. It installs nothing. Each ✓ says what it rests on, e.g. "login not…