Install Scripts

Trigger

• Keywords: install scripts, setup scripts, copy scripts, install-scripts

When NOT to Use

• Installing rules (use /install-rules)
• Installing hooks (use /install-hooks)
• Full project setup (use /project-setup)

Workflow

Phase 0: Resolve mode; obsolete-set migration (first for non-list invocations; --dry-run forwarded)
Phase 1: Locate plugin scripts dir
Phase 2: Enumerate scripts (core + skill scripts)
Phase 3: Determine install set (--all, --skill, specific names)
Phase 4: Copy scripts + dependencies to .claude/scripts/
Phase 4.5: Update manifest
Phase 5: Output report

Phase 0: Obsolete-Set Migration

Same shared migration /install-hooks runs, invoked here too so neither entry point can reproduce the unsafe order by hand (hook-lightweighting § 3.6). Resolve the invocation mode first: a listing invocation skips this phase (read-only), and --dry-run is forwarded so the migration also only reports:

# --dry-run → append --dry-run to the command below; list-only invocations skip Phase 0
node "${CLAUDE_PLUGIN_ROOT}/scripts/migrate-hook-lightweighting.js" --repo "$(git rev-parse --show-toplevel)"

It deregisters obsolete settings entries first and deletes the retired enforcement-layer files only after the settings writes succeed. On exit 1, stop the install and surface the report. Include the migration's report lines in Phase 5's output.

Arguments

$ARGUMENTS

Script Types

Conflict Handling

Output

## Install Scripts Report

| Script | Type | Status |
|--------|------|--------|
| precommit-runner.js | core | installed |
| lib/utils.js | core-lib | up to date |
| git-profile.sh | skill | installed |

Installed: N | Skipped: M | Conflicts: K