verify-setup — Claude Code command: infrastructure health check and repair
verify-setup — a command that diagnoses your project's infrastructure, identifies what's broken, and guides you through fixes. Use it when Claude Code hooks, dependencies or configs fail.
MIT ★ 10,055 updated 2026-07-13
.claude/commands/verify-setup.mdWhat verify-setup does
verify-setup runs a health check on your project: missing dependencies, script permissions, JSON syntax in .claude/settings.json and .claude/skills/skill-rules.json, hook registration. The script reports each failure with a specific fix.
Each [FAIL] line includes a remedy: run npm install in .claude/hooks/ for missing packages, add execute bits with chmod +x for scripts, fix JSON syntax (often a trailing comma). If hooks lack registration in settings.json, the command asks whether to copy them from the showcase repository or remove dead registrations.
Warnings ([WARN]) flag optional features — session intelligence, jq-based file tracking, AI classification keys — which the script lists but does not install, letting you decide.
What it helps with
- Identify broken dependencies and missing npm packages
- Fix file permissions on
.claude/hooks/scripts - Validate and repair JSON syntax in config files
- Register hooks or remove orphaned entries from settings.json
- Diagnose which parts of the infrastructure need attention
Example prompts for the agent
- Run the health check and show me what's broken
- Check the Claude Code infrastructure and fix anything failing
- Execute verify-setup and help me understand the errors
How to install verify-setup
Manually: put the files in place
.claude/commands/verify-setup.mdCall it with /verify-setup. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/verify-setup.mdCall it with /prompts:verify-setup. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/verify-setup.prompt.mdManually: put the files in place
.gemini/commands/verify-setup.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about verify-setup
How do I install verify-setup in Claude Code?
Copy .claude/commands/verify-setup.md to your project root. For Codex, place ~/.codex/prompts/verify-setup.md in your home directory. For GitHub Copilot, add .github/prompts/verify-setup.prompt.md to the repo. For Gemini CLI, put .gemini/commands/verify-setup.toml in config.
What does verify-setup check?
It validates dependencies, script permissions, JSON files, and hook registration. When it finds issues, it prints the exact steps to fix them.
What are [WARN] lines?
Warnings for optional features like session intelligence or AI classification keys. The command lists what each one does; you choose whether to enable them.
Source text
verify-setup.md · MIT
--- description: Run the infrastructure health check and fix anything that fails argument-hint: (no arguments needed) --- Run the Claude Code infrastructure health check and get it fully green. ## Steps 1. Run the health check from the project root: ```bash bash .claude/scripts/verify-setup.sh ``` 2. For every `[FAIL]` line, apply the printed fix. Common fixes: - Dependencies missing: `cd .claude/hooks && npm install` - Scripts not executable: `chmod +x .claude/hooks/*.sh` - Invalid JSON in `.claude/settings.json` or `.claude/skills/skill-rules.json`: read the file, find the syntax error (usually a trailing comma), and repair it without changing any settings values - Missing hook scripts registered in settings.json: ask the user whether to copy them from the showcase repo (https://github.com/diet103/claude-code-infrastructure-showcase) or remove the dead registrations 3. Re-run the script after each fix until it reports 0 failed. 4. `[WARN]` lines are optional features (session intelligence, jq-based file tracking, AI classification keys). Do NOT install API keys or system packages on the user's behalf - summarize what each warning means and let the user decide. 5. Report the final result to the user: what was broken, what you fixed, and what (if anything) remains as a warning.
© diet103 · MIT · diet103/claude-code-infrastructure-showcase