Test run
Run plugin test suites in this monorepo and report a concise pass/fail summary. Optional plugin slug arg; without arg, runs all plugins under plugins/.From its SKILL.md
npx -y skills add gtapps/claude-code-hermit --skill test-runAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
2.3 KB, as published. Nobody here has run it
Test Run
Run plugin test suites and report a concise summary. Operates on a single plugin when given a slug; otherwise loops every plugin in plugins/.
Usage
/test-run — run tests for every plugin in plugins/ and report a per-plugin summary plus an overall PASS/FAIL.
/test-run <plugin-slug> — run tests for just that plugin.
Examples:
/test-run claude-code-hermit/test-run claude-code-homeassistant-hermit
Steps
0. Resolve target slugs
- If no slug arg was passed, run
bash scripts/test-all.shfrom the repo root (launches every plugin's suite in parallel; wall time is bounded by the slowest suite instead of their sum) and report its summary table directly — skip Steps 0-1 below entirely. - If a slug arg was passed, validate
plugins/<slug>/.claude-plugin/plugin.jsonexists. If not, abort with:Plugin 'plugins/<slug>/' not found. Available: <comma-separated slugs>.Then continue to Step 1 for that single plugin.
1. Run the suite (single-plugin arg only)
Plugins ship one of two test conventions. Detect and dispatch:
- Bash entrypoint — if
plugins/<slug>/tests/run-all.shexists (dev/fitness/scribe/forge convention):bash plugins/<slug>/tests/run-all.sh 2>&1 - Bun entrypoint — else if any
plugins/<slug>/tests/*.test.tsexists (core/HA/feed convention):cd plugins/<slug> && bun test 2>&1. - Neither marker — mark
no tests configuredand continue.
Capture full output. Extract pass/fail counts from the suite's summary line.
2. Report
Per-plugin block:
=== <slug> ===
Hook tests: X passed, Y failed (bash convention only)
Contract tests: X passed, Y failed (bash convention only)
Script tests: X passed, Y failed (bash convention only)
Bun tests: X passed, Y failed (bun convention only)
Plugin result: PASS / FAIL / SKIP
Final overall line:
Overall: PASS / FAIL (<n> passed, <m> failed, <k> skipped across <p> plugins)
If any test failed, include the failure details below the summary so the developer can act on them immediately.