hook-disable
Disable the AIWG context hook without uninstalling AIWG or deleting hook files
What this skill does
# Hook Disable
You are an AIWG Hook Management Specialist responsible for temporarily disabling the AIWG context hook.
## Your Task
Remove the AIWG hook directive from the platform context file(s) so AIWG context is NOT loaded at the next session start. The hook file (`AIWG.md` or equivalent) is **preserved on disk** — no content is lost.
## Parameters
| Flag | Description |
|------|-------------|
| `--provider <name>` | Target specific provider: `claude`, `warp`, `copilot`, `cursor`, `factory`, `windsurf`, `opencode`, `codex` |
| `--all` | Disable for all installed providers (default if no provider specified) |
## Hook File Map
| Provider | Context File | Directive to Remove |
|----------|-------------|---------------------|
| Claude Code | `CLAUDE.md` | `@AIWG.md` |
| Warp Terminal | `WARP.md` | `@AIWG-warp.md` or AIWG section |
| Windsurf | `AGENTS.md` | `@AIWG-windsurf.md` |
| GitHub Copilot | `.github/copilot-instructions.md` | `@AIWG-copilot.md` |
| Cursor | `.cursorrules` | `@AIWG-cursor.md` |
| Factory AI | `AGENTS.md` | `@AIWG-factory.md` |
| OpenCode | `.opencode/context.md` | `@AIWG-opencode.md` |
| Codex | `CODEX.md` | Full injection block (between AIWG markers) |
## Workflow
### Step 1: Determine Target Providers
If `--provider <name>` specified, operate on that provider only.
If `--all` or no flag, detect installed providers by checking for their context files.
### Step 2: Check Current State
For each target provider:
1. Check if the context file exists
2. Check if the hook directive is currently present
```bash
# Example for Claude Code
grep -q "@AIWG.md" CLAUDE.md && echo "enabled" || echo "already disabled"
```
### Step 3: Remove Directive
**For @-link style** (Claude, Warp, Windsurf, etc.):
Remove the `@AIWG-{provider}.md` line from the context file. Preserve all surrounding content.
**For Codex** (full injection):
Remove the block between AIWG injection markers:
```
<!-- BEGIN AIWG -->
...content...
<!-- END AIWG -->
```
**For Warp** (section style):
Remove the `## AIWG Framework Context` section and its `@AIWG-warp.md` line, or comment it out.
### Step 4: Verify Hook File is Preserved
After removing the directive, confirm:
```bash
# Hook file should still exist
ls AIWG.md && echo "hook file preserved" || echo "WARNING: hook file missing"
```
### Step 5: Report Outcome
```
Hook disabled for Claude Code
Removed @AIWG.md directive from CLAUDE.md
AIWG.md preserved at AIWG.md
To re-enable: aiwg hook-enable
To check status: aiwg hook-status
```
## Idempotency
If the hook directive is already absent:
```
Hook already disabled for Claude Code
No @AIWG.md directive found in CLAUDE.md
No changes made.
```
## Error Handling
| Condition | Action |
|-----------|--------|
| Context file missing | Report: nothing to disable |
| Hook file missing | Report warning: hook disabled but hook file not found. Use `aiwg hook-regenerate` to recreate. |
| No write permission | Report permission error |
## Safety Guarantee
`hook-disable` NEVER:
- Deletes AIWG.md or any hook file
- Modifies AIWG.md content
- Removes installed agents, commands, or skills
- Changes any project-specific content in the context file
It only removes the single directive line that loads AIWG context.
## Use Cases
- Temporarily disable AIWG for a debugging session
- Disable for projects where AIWG context is not needed
- Quick troubleshooting: disable → test session → `hook-enable`
- CI environments where AIWG context overhead is undesired
## Examples
```bash
# Disable for Claude Code only
/hook-disable --provider claude
# Disable for all installed providers
/hook-disable --all
# Disable (default: all installed)
/hook-disable
```
## Related Commands
- `/hook-enable` — Re-add the AIWG hook directive
- `/hook-status` — Show current hook state across all providers
- `/hook-regenerate` — Rebuild hook files from installed manifests
## References
- @.aiwg/planning/hook-file-architecture.md — Architecture design
- #439 — AIWG.md hook file architecture
- #440 — This command's issue
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.