plugins/claude-code-dev-hermit/skills/dev-test/SKILL.md
Run the configured test suite and record the result to .claude-code-hermit/state/last-test.json. /dev-pr reads this record; a fresh pass at HEAD skips re-running. Use for mid-task verification, debugging a failing test in isolation, or as a building block for /dev-quality.
npx skillsauth add gtapps/claude-code-hermit dev-testInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Run the project's configured test command and record the result.
Optional --cwd <path>. When set, the test command runs from <path> and last-test.json records <path>'s HEAD SHA. Use this for nested-repo workflows (see CLAUDE-APPEND §Implementation Flow). <path> must be a git working tree.
Run the following Bash command. Use timeout: 600000 (10-min ceiling). Append --cwd "<path>" when the operator passed --cwd.
node "${CLAUDE_PLUGIN_ROOT}/scripts/record-test-result.js" run
If exit 0: report tests: pass.
If exit 1 and stderr is "commands.test not configured": tell the operator to set commands.test in .claude-code-hermit/config.json (or re-run /claude-code-dev-hermit:hatch).
If exit non-zero for any other reason: report tests: FAIL (exit N) with the last 10 lines of output.
/dev-pr invokes the same machinery on cache miss — running /dev-test first is optional but warms the cache (a second /dev-pr call at the same HEAD skips the test run entirely).
For suites longer than 10 min (Bash ceiling): run the test command directly in a terminal, then record the result manually:
node <CLAUDE_PLUGIN_ROOT>/scripts/record-test-result.js write <exit_code> <duration_ms>
Then re-run /dev-pr.
tools
Presence history & tracker-health report — current home/away state, reliability, recent arrival/departure transitions, and activity patterns for person/device_tracker entities. Use when the operator asks about presence history or when a presence-dependent automation (locks, alarm, vacuum, climate) misbehaves.
development
Evening house brief — end-of-day security check, device status, and energy snapshot. Runs as a daily routine at 22:30 or on demand.
tools
Browse and explain the hermit's Home Assistant automations — list by topic, filter by keyword with plain-language YAML explanations, or sort by last-fired. Read-only. Use when the operator asks "what automations do I have / what does this one do / which haven't fired."
tools
On-demand HA-voice brainstorm — reads entity inventory, automation/script listings, and operator intent to surface at most 2 capability-gap ideas, each gated by proposal-triage before becoming a PROP. Invoke when the operator asks "what automations am I missing?", "any coverage gaps?", or "brainstorm improvements". Never runs autonomously.