install-hooks

Files (1)

• SKILL.md

SKILL.md (first lines)

# X-7 installable hooks bundle (§23 amendment)

Writes packaged hooks + slash commands + agents + detectors to the
target `settings.json`. Uninstall metadata block stamped at install
time so the cleanup path (O-3) can restore prior state without
auto-deleting audit-log or evidence directories.

## Invocation

```
/install-hooks [--scope user|project] [--include <component>...] [--dry-run] [--force]
```

- `--scope user|project` — install to `~/.claude/settings.json` (user)
  or `.claude/settings.json` (project). Default: `project`.
- `--include <component>` — install only this component (repeatable).
  Components: `hooks`, `commands`, `agents`, `detectors`.
- `--dry-run` — emit plan; no settings.json writes (per §2.14).
- `--force` — override the conflict refusal when target already has
  conflicting hook scripts. Logged to C-4 with conflict diff.

## Uninstall metadata block

```json
{
  "tdd_pro_installed_at": "<ISO 8601>",
  "tdd_pro_components": ["hooks", "commands", "..."],
  "tdd_pro_version": "<semver>",
  "tdd_pro_signature": "<sha256>"
}
```

## Idempotency

Re-running with no version change is a no-op. On version change,
runs the appropriate `migrations/<from>-to-<to>.sh` per O-3.

## Cross-references

- §23 v1.9.1 amendment (this skill)
- O-3 /uninstall-cleanup
- C-4 audit log
- §2.14 destructive command dry-run subjects

From drumfiend21/claude-tdd-pro, Apache-2.0.

More from drumfiend21/claude-tdd-pro