Agent skill
install-hooks
Install plugin hooks into project .claude/ for persistent use without plugin loaded
Install this agent skill to your Project
npx add-skill https://github.com/sd0xdev/sd0x-dev-flow/tree/main/skills/install-hooks
SKILL.md
Install Hooks
Trigger
- Keywords: install hooks, setup hooks, copy hooks, install-hooks
When NOT to Use
- Installing rules (use
/install-rules) - Installing scripts (use
/install-scripts) - Full project setup (use
/project-setup)
Workflow
Phase 1: Locate plugin hooks dir
Phase 2: Enumerate hook scripts
Phase 3: Determine install set (--all, specific names, or interactive)
Phase 4a: Copy scripts to .claude/hooks/
Phase 4b: Merge hook definitions into settings.json
Phase 4c: Update manifest
Phase 4.5: Backfill CLAUDE.md references
Phase 5: Output report
Arguments
$ARGUMENTS
| Argument | Description |
|---|---|
--all |
Install all available hooks |
--list |
List available hooks without installing |
--dry-run |
Show what would be installed, no changes |
--force |
Overwrite existing hooks with different content |
--local |
Write to settings.local.json instead of settings.json |
--guard-mode warn|strict |
Set stop-guard mode during install |
hook-names... |
Specific hooks to install |
Two-Layer Install
| Layer | Target | Content |
|---|---|---|
| Scripts | .claude/hooks/*.sh |
Executable hook scripts |
| Definitions | settings.json hooks entries |
Event → script path mapping |
Conflict Handling
| Script Status | Settings Status | Action |
|---|---|---|
| Missing | Missing | Install both |
| Identical | Present | Skip (up to date) |
| Different | Present | AskUserQuestion |
Output
## Install Hooks Report
| Hook | Script | Settings | Status |
|------|--------|----------|--------|
| post-edit-format | ✅ | ✅ | installed |
| stop-guard | ✅ | ⏭️ | skipped (identical) |
Scripts: N installed | Settings entries: M merged
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
runbook
Generate and update feature release runbooks from existing docs and codebase. Use when: creating operational runbook, release handbook, deployment checklist, pre-release preparation. Not for: incident response (v2), code review (use codex-code-review), architecture design (use architecture).
ask
Context-aware Q&A with auto context gathering. Use when: user has a quick question about codebase, git history, rules, docs, or skills during development. Not for: code changes (use feature-dev), code review (use codex-review-fast), deep research (use deep-research), full code trace (use code-explore). Output: structured answer with source attribution.
project-brief
Convert a technical spec into a PM/CTO-readable executive summary. Simplify technical details, focus on business value.
codex-test-gen
Generate unit tests for specified functions using Codex MCP
bug-fix
Bug fix workflow. Use when: fixing bugs, resolving issues, regression fixes. Not for: new features (use feature-dev), understanding code (use code-explore). Output: fix + regression test + review gate.
skill-health-check
Validate skill quality against routing, progressive loading, and verification criteria. Use when: auditing skills, checking skill health, reviewing skill design. Not for: code review (use codex-code-review) or doc review (use doc-review). Output: health report with per-skill ratings + Gate.
Didn't find tool you were looking for?