arthai-marketplace

/extensions disable

Disable a previously enabled compliance extension pack.

Synopsis

/extensions disable <pack_id> [reason]

When to use it

A pack no longer applies to this project (out of scope, requirements changed)
Temporarily pausing a pack you plan to re-enable under a different scope
Not for: skipping a single rule while keeping the rest of the pack active — use /extensions waive instead. Use disable when the whole pack no longer applies; use waive when only one rule in it doesn’t.

pack_id must be the full domain/name form shown by /extensions list (e.g. compliance/hipaa) — a bare name like hipaa won’t match.

Quickstart

/extensions disable compliance/hipaa "Out of scope for this project"

What you’ll see:

Archived evidence to .claude/extensions/compliance-hipaa/archive/2026-07-05T00-00-00Z/   (only if a report existed)
Disabled compliance/hipaa (reason: Out of scope for this project).
To re-enable: /extensions enable compliance/hipaa

The pack’s rules stop contributing to skill prompts, its current evidence report is archived (if one existed), and the audit trail is preserved.

Examples

/extensions disable compliance/hipaa "Out of scope for this project"   # disable with inline reason
/extensions disable security/baseline                                  # no reason given — you'll be asked for one

What it does

Collects a reason — if you didn’t supply one, prompts you with a dropdown menu of common reasons (e.g. “Out of scope for this project”), plus a free-text and a cancel option. This is a user-confirmation checkpoint: a reason is required for the audit trail, and you can cancel out of it.
Validates the pack is currently enabled — disabling a pack that isn’t enabled (or is already disabled) exits cleanly (idempotent).
Marks the entry disabled in .claude/extensions/.enabled.json with timestamp and reason — the original entry is updated, never deleted, so a later re-enable keeps the full history.
Archives the evidence report (if one exists) to .claude/extensions/<pack-kebab>/archive/<timestamp>/.
Confirms, printing Disabled {pack_id} (reason: {reason}). followed by To re-enable: /extensions enable {pack_id} — re-enabling regenerates evidence from scratch.

Output & artifacts

Updated .claude/extensions/.enabled.json — entry marked with disabled_at and disabled_reason
.claude/extensions/<pack-kebab>/archive/<timestamp>/evidence-report.md — archived evidence (when one existed)

Troubleshooting

Problem	Fix
`Pack {pack_id} is not currently enabled`	Nothing to disable — check /extensions status for what’s active
`Reason required`	Re-invoke with a quoted reason: `/extensions disable <pack> "why"`
`jq required for /extensions disable`	Install `jq` — this command manipulates JSON state
`Could not acquire lock`	Another `/extensions` command is running; if not, remove `.claude/extensions/.lock`

/extensions enable — re-enable later; the prior disable is preserved in the audit trail
/extensions list — all packs on disk, enabled or not
/extensions status — operational detail for enabled packs
/extensions waive — narrower alternative: waive one rule, keep the pack