← ClaudeAtlas

dxkit-hookslisted

Install, configure, troubleshoot, or remove dxkit git hooks. Use when the user asks "set up hooks", "pre-push isn't firing", "how do I chain with husky", "bypass the hook", or anything about pre-commit/pre-push behavior in a dxkit-managed repo.
vyuh-labs/dxkit · ★ 2 · Code & Development · score 68
Install: claude install-skill vyuh-labs/dxkit
# dxkit-hooks This skill handles the git-hook surface dxkit ships. Use it to install hooks, debug "the hook didn't fire," chain dxkit with an existing hook system, or guide a bypass. ## What dxkit ships `.githooks/pre-push` (default-on under `--full`) — runs the guardrail check before code leaves the developer's machine. Fast on warm scanner caches (~10-30s). `.githooks/pre-commit` (opt-in via `--with-precommit-hook`) — same guardrail check but on every commit. Slower on large repos (~1-3 min on 500+ file repos). Not in `--full` by default because the wall-clock cost gates adoption. Both run `npx vyuh-dxkit guardrail check`. The check exits 1 (blocking) on net-new findings vs. the baseline. ## Installation ```bash # Pre-push only (recommended for most teams) npx vyuh-dxkit init --with-hooks --yes # Both pre-commit + pre-push npx vyuh-dxkit init --with-hooks --with-precommit-hook --yes # Add to an existing dxkit install (idempotent) npx vyuh-dxkit init --with-precommit-hook --yes ``` Existing hooks at `.githooks/<name>` or `.husky/<name>` trigger sidecar-write mode: dxkit puts its hook at `.githooks/<name>.dxkit` and emits a chain note instead of clobbering. ## Activation Hooks activate by setting `core.hooksPath = .githooks` in the local git config. Dxkit wires this via `npm postinstall` so every clone + `npm install` runs it automatically. Manual: ```bash # Either of these works npx vyuh-dxkit hooks activate git config core.hooksPath .githooks ``` `npx vyuh-dxk