verify-claude-setup

To verify your .claude configuration, run a readiness check that validates expected file counts, required agent filenames, settings.json hook wiring, and memory presence to ensure proper operation. This produces a summary report of configuration completeness.

A .claude directory configuration audit includes validating agent definitions for required structure, checking hook scripts for executable permissions, verifying rules and memory files exist, and counting slash commands for workflow readiness. It reports any missing or misconfigured elements.

Claude agents may misbehave after updates due to missing or partially updated configuration files. Troubleshooting by auditing the .claude directory detects missing rules, broken hook wiring in settings.json, or absent memory files causing the unintended behavior.

To check if Claude hooks are properly wired, verify hook script presence, confirm basic executable and shebang requirements are met, and validate that the hook wiring is accurately reflected in settings.json. This ensures hooks trigger correctly during agent operations.

You should run a pre-flight check on your Claude agents and rules before starting complex agent workflows or launching major tasks in hyper-forge. This prevents failures caused by missing agents, unimported research-first rules, or incomplete memory configurations.

Yes, you can use configuration verification for troubleshooting missing Claude commands by estimating whether slash commands are populated and organized. The readiness status report highlights missing command files and incomplete directory structures before you start work.