Stats
Actions
Tags
From sd0x-dev-flow
Installs plugin hooks into a project's .claude/ directory for persistent use without the plugin loaded. Supports selective or bulk install, dry-run, and conflict resolution.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sd0x-dev-flow:install-hooksThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Keywords: install hooks, setup hooks, copy hooks, install-hooks
/install-rules)/install-scripts)/project-setup)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
| 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 |
| Layer | Target | Content |
|---|---|---|
| Scripts | .claude/hooks/*.sh | Executable hook scripts |
| Definitions | settings.json hooks entries | Event → script path mapping |
| Script Status | Settings Status | Action |
|---|---|---|
| Missing | Missing | Install both |
| Identical | Present | Skip (up to date) |
| Different | Present | AskUserQuestion |
## Install Hooks Report
| Hook | Script | Settings | Status |
|------|--------|----------|--------|
| post-edit-format | ✅ | ✅ | installed |
| stop-guard | ✅ | ⏭️ | skipped (identical) |
Scripts: N installed | Settings entries: M merged
npx claudepluginhub sd0xdev/sd0x-dev-flow --plugin sd0x-dev-flowScaffolds Claude Code hooks with templates, validation, and conflict analysis. Analyzes existing hooks, prevents conflicts, and generates boilerplate code automatically.
Configures event-driven hooks for Claude Code to run shell commands before/after tool calls, on lifecycle events, or user prompts for automations and validations.
Guides creation of Claude Code plugin hooks with prompt-based and bash command types for PreToolUse, PostToolUse, Stop, and other events. Covers plugin hooks.json and settings.json formats.