← ClaudeAtlas

hook-stocktakelisted

Audit the harness hooks (hooks/*.sh, scripts/hooks/*) and their settings.json wiring, and give each a verdict (hook の棚卸し).
shimo4228/claude-harness · ★ 4 · AI & Automation · score 83
Install: claude install-skill shimo4228/claude-harness
# hook-stocktake — Hook Quality Audit Evaluate every hook of the harness and assign each a verdict: `Keep / Improve / Update / Merge / Dissolve / Retire`. A hook's cost is unlike a skill's or a rule's: it runs unattended on every matching event, it can block, and it reads repo-controlled data (paths, commit metadata, tool input). So the questions are wiring, evidence that it still earns its place, test coverage, and its share of the harness threat surface (rule `security.md`). **Roots.** `<harness>` below is the harness this audit covers: `~/.claude` by default, or a repository's `.claude/` when skill `harness-stocktake` runs in project mode (its Roots section maps the paths, names the evidence that is `n/a` there, and says which convention checks apply). The ledger `<ledger>` belongs to that harness: `${CLAUDE_SKILL_DIR}/results.json` when this skill's directory is inside `<harness>` (the harness carries its own copy of the skill), else `<harness>/stocktake/hook-stocktake.json` (an installed plugin, or project mode). Either way it is committed with the harness's other changes on the apply branch. The paths and conventions below are the author's harness layout. In another setup, map each target to where that setup keeps its hooks, and record a check whose input the setup does not have (`harness_lint.py`, `hooks/README.md`, `tests/*.bats`, the usage-logging hooks, rule `security.md`) as `—`, not as a No. ## Phase 1 — Inventory and wiring (deterministic) Build the inventor