agentleFS
searlscosearlsco/prove_it/.claude/skills/test-local/SKILL.md

test-local

Skill198 starsChanged 8 months agoMITView on GitHub

Test prove_it from source against an example project or temp directory. Use when you want to verify hook behavior end-to-end without a Homebrew release.

  • Deletes or force-pushes
  • Installs packages

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. microsoft/agent365-skills★ 50same name
    2. alex-voloshin-dev/ai-skills★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

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

    line 8
  2. Distinctive:

    Run the requested test. Common scenarios:

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.