prove_it: Skill for Claude Code

Test prove_it locally

Run prove_it from the repo source (not the Homebrew install) to test hook behavior.

Steps

1. Identify the test target. If the user didn't specify, use example/basic/.

2. Set up the PATH shim so prove_it resolves to the repo's cli.js:

   export PATH="$(git rev-parse --show-toplevel)/test/bin:$PATH"
   which prove_it   # should show test/bin/prove_it
   

3. Run the requested test. Common scenarios:

   Test a specific hook event:

   cd example/basic
   echo '{"hook_event_name":"Stop","session_id":"test","cwd":"."}' | prove_it hook claude:Stop
   

   Test SessionStart:

   echo '{"hook_event_name":"SessionStart","source":"startup","session_id":"test","cwd":"."}' | prove_it hook claude:SessionStart
   

   Test PreToolUse (edit protection):

   echo '{"hook_event_name":"PreToolUse","tool_name":"Edit","tool_input":{"file_path":"src/greet.js"},"session_id":"test","cwd":"."}' | prove_it hook claude:PreToolUse
   

   Test PreToolUse (commit gate):

   echo '{"hook_event_name":"PreToolUse","tool_name":"Bash","tool_input":{"command":"git commit -m test"},"session_id":"test","cwd":"."}' | prove_it hook claude:PreToolUse
   

   Test init in a temp directory:

   tmpdir=$(mktemp -d)
   cd "$tmpdir" && git init
   prove_it init --no-default-checks
   cat .claude/prove_it/config.json
   prove_it deinit
   rm -rf "$tmpdir"
   

   Test doctor:

   cd example/basic
   prove_it doctor
   

4. Report the output and whether the behavior matches expectations.

Notes

• The shim at test/bin/prove_it just does exec node ../../cli.js "$@"
• All $(prove_it prefix)/libexec/* commands in configs will also resolve through the shim
• This tracks with the current git ref—check out any commit to test that version