oh-my-copilot 4.13.2 → 4.13.21

package/skills/ai-slop-cleaner/SKILL.md

@@ -1,135 +1,133 @@
 ---
 name: ai-slop-cleaner
-description: Clean AI-generated code slop with a test-first, deletion-first deslop workflow and optional reviewer-only mode
+description: Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode
+level: 3
 ---
 
-<Purpose>
-Use this skill to systematically clean AI-generated code slop without changing intended behavior. It focuses on simplifying existing code by deleting dead code, collapsing duplicates, removing needless abstractions, tightening boundaries, and reinforcing tests before and after cleanup.
-</Purpose>
-
-<Use_When>
-- The user explicitly says "deslop", "anti-slop", or "AI slop"
-- The request is to clean up or refactor code that feels bloated, repetitive, or overly abstract
-- The user wants a reviewer-only anti-slop pass via `--review` after cleanup work is drafted
-- The user calls out duplicate code, dead code, wrapper layers, boundary violations, or weak regression coverage
-- The goal is simplification, deletion, and cleanup rather than adding new features
-</Use_When>
-
-<Do_Not_Use_When>
-- The task is primarily a new feature build -- use `autopilot` or direct implementation instead
-- The user wants a broad architecture redesign rather than an incremental cleanup pass
-- The request is a generic refactor with no cleanup/simplification intent
-- Behavior is unclear and there are no tests or concrete anchors -- clarify scope first
-</Do_Not_Use_When>
-
-<Why_This_Exists>
-AI-generated code often works while still adding avoidable complexity: duplicate helpers, dead branches, wrapper layers, inconsistent naming, boundary leaks, and missing tests. This skill enforces a disciplined cleanup workflow so simplification happens deliberately instead of as vague "refactoring" that might expand scope.
-</Why_This_Exists>
-
-<Review_Mode>
-### Review Mode (`--review`)
-`--review` activates an explicit reviewer pass after the cleanup writer pass.
+# AI Slop Cleaner
+
+Use this skill to clean AI-generated code slop without drifting scope or changing intended behavior. In OMC, this is the bounded cleanup workflow for code that works but feels bloated, repetitive, weakly tested, or over-abstracted.
+
+## When to Use
+
+Use this skill when:
+- the user explicitly says `deslop`, `anti-slop`, or `AI slop`
+- the request is to clean up or refactor code that feels noisy, repetitive, or overly abstract
+- follow-up implementation left duplicate logic, dead code, wrapper layers, boundary leaks, or weak regression coverage
+- the user wants a reviewer-only anti-slop pass via `--review`
+- the goal is simplification and cleanup, not new feature delivery
+
+## When Not to Use
+
+Do not use this skill when:
+- the task is mainly a new feature build or product change
+- the user wants a broad redesign instead of an incremental cleanup pass
+- the request is a generic refactor with no simplification or anti-slop intent
+- behavior is too unclear to protect with tests or a concrete verification plan
+
+## OMC Execution Posture
+
+- Preserve behavior unless the user explicitly asks for behavior changes.
+- Lock behavior with focused regression tests first whenever practical.
+- Write a cleanup plan before editing code.
+- Prefer deletion over addition.
+- Reuse existing utilities and patterns before introducing new ones.
+- Avoid new dependencies unless the user explicitly requests them.
+- Keep diffs small, reversible, and smell-focused.
+- Stay concise and evidence-dense: inspect, edit, verify, and report.
+- Treat new user instructions as local scope updates without dropping earlier non-conflicting constraints.
+
+## Scoped File-List Usage
+
+This skill can be bounded to an explicit file list or changed-file scope when the caller already knows the safe cleanup surface.
+
+- Good fit: `oh-my-copilot:ai-slop-cleaner skills/ralph/SKILL.md skills/ai-slop-cleaner/SKILL.md`
+- Good fit: a Ralph session handing off only the files changed in that session
+- Preserve the same regression-safe workflow even when the scope is a short file list
+- Do not silently expand a changed-file scope into broader cleanup work unless the user explicitly asks for it
+
+## Ralph Integration
+
+Ralph can invoke this skill as a bounded post-review cleanup pass.
+
+- In that workflow, the cleaner runs in standard mode (not `--review`)
+- The cleanup scope is the Ralph session's changed files only
+- After the cleanup pass, Ralph re-runs regression verification before completion
+- `--review` remains the reviewer-only follow-up mode, not the default Ralph integration path
+
+## Review Mode (`--review`)
+
+`--review` is a reviewer-only pass after cleanup work is drafted. It exists to preserve explicit writer/reviewer separation for anti-slop work.
 
 - **Writer pass**: make the cleanup changes with behavior locked by tests.
-- **Reviewer pass (`--review`)**: inspect the result for duplication, dead code, boundary violations, missing tests, and unnecessary abstractions.
-- The same pass must not both write and self-approve without a separate review step.
+- **Reviewer pass**: inspect the cleanup plan, changed files, and verification evidence.
+- The same pass must not both write and self-approve high-impact cleanup without a separate review step.
 
 In review mode:
-1. Do **not** make edits first.
-2. Inspect the cleanup plan, changed files, and regression coverage.
+1. Do **not** start by editing files.
+2. Review the cleanup plan, changed files, and regression coverage.
 3. Check specifically for:
    - leftover dead code or unused exports
-   - duplicate logic that was not consolidated
+   - duplicate logic that should have been consolidated
    - needless wrappers or abstractions that still blur boundaries
    - missing tests or weak verification for preserved behavior
-   - risky cleanup that changed behavior without explicit intent
+   - cleanup that appears to have changed behavior without intent
 4. Produce a reviewer verdict with required follow-ups.
-5. If changes are needed, hand them back to a separate writer/executor pass instead of fixing and approving in one pass.
-
-This mode exists to preserve writer/reviewer separation: the authoring pass changes code, the reviewer pass evaluates whether the cleanup actually reduced slop safely.
-</Review_Mode>
-
-<Execution_Policy>
-- Preserve behavior unless the user explicitly asks for behavior changes
-- Lock behavior with regression tests first whenever practical
-- Write a cleanup plan before editing code
-- Prefer deletion over addition
-- Reuse existing utilities and patterns before introducing anything new
-- Avoid new dependencies unless the user explicitly requests them
-- Keep diffs small, reversible, and smell-focused
-- Keep writer/reviewer separation: author in one pass, review in another
-- Verify with lint/typecheck/tests/static analysis relevant to the touched area
-</Execution_Policy>
-
-<Steps>
-1. **Lock behavior first**
-   - Identify the current behavior and add or strengthen regression tests before cleanup when practical
-   - If tests cannot be added first, record the verification plan explicitly before editing
-
-2. **Create a cleanup plan**
-   - Do not start coding immediately
-   - List the targeted smells and the files likely involved
-   - Sequence cleanup passes from lowest-risk deletion to higher-risk consolidation
-
-3. **Categorize the slop**
-   - Duplicate code
-   - Dead or unused code
-   - Needless abstraction / wrapper layers
-   - Boundary violations / misplaced responsibilities
-   - Missing or weak tests
-
-4. **Execute one smell-focused pass at a time**
-   - **Pass 1: Dead code deletion** -- remove unused branches, helpers, exports, and stale comments
-   - **Pass 2: Duplicate removal** -- consolidate repeated logic into existing patterns where possible
-   - **Pass 3: Naming and error-handling cleanup** -- tighten naming, trim noisy plumbing, normalize obvious inconsistencies
-   - **Pass 4: Test reinforcement** -- fill any regression gaps revealed by the cleanup
-
-5. **Run quality gates**
-   - Run the relevant lint, typecheck, unit/integration tests, and any static or security checks already present for the touched area
-   - If a gate fails, fix the underlying issue or revert the risky cleanup instead of forcing it through
-
-6. **Optional `--review` pass**
-   - Run a distinct reviewer pass that checks duplication, dead code, boundary violations, test coverage, and needless abstractions
-   - If the reviewer finds issues, address them in a follow-up cleanup pass before closing the task
-
-7. **Report outcome**
-   - Changed files
-   - Simplifications made
-   - Behavior locked by tests
-   - Remaining risks or slop intentionally left for a later pass
-</Steps>
-
-<Examples>
-<Good>
-User: "deslop this module -- too many wrappers, duplicate helpers, and dead code"
-Why good: Explicit anti-slop intent with concrete cleanup smells.
-</Good>
-
-<Good>
-User: "cleanup the AI slop in src/auth: remove dead code and tighten boundaries"
-Why good: Cleanup/refactor request is clearly about simplification, not feature work.
-</Good>
-
-<Bad>
-User: "refactor auth to support SSO"
-Why bad: This is feature work disguised as refactoring, not anti-slop cleanup.
-</Bad>
-
-<Bad>
-User: "clean up formatting"
-Why bad: Formatting-only work does not need the full anti-slop workflow.
-</Bad>
-</Examples>
-
-<Final_Report>
-Always end with:
-- **Changed files**
-- **Simplifications**
-- **Verification run**
-- **Remaining risks**
-</Final_Report>
-
-<Usage>
+5. Hand needed changes back to a separate writer pass instead of fixing and approving in one step.
+
+## Workflow
+
+1. **Protect current behavior first**
+   - Identify what must stay the same.
+   - Add or run the narrowest regression tests needed before editing.
+   - If tests cannot come first, record the verification plan explicitly before touching code.
+
+2. **Write a cleanup plan before code**
+   - Bound the pass to the requested files or feature area.
+   - List the concrete smells to remove.
+   - Order the work from safest deletion to riskier consolidation.
+
+3. **Classify the slop before editing**
+   - **Duplication** — repeated logic, copy-paste branches, redundant helpers
+   - **Dead code** — unused code, unreachable branches, stale flags, debug leftovers
+   - **Needless abstraction** — pass-through wrappers, speculative indirection, single-use helper layers
+   - **Boundary violations** — hidden coupling, misplaced responsibilities, wrong-layer imports or side effects
+   - **Missing tests** — behavior not locked, weak regression coverage, edge-case gaps
+
+4. **Run one smell-focused pass at a time**
+   - **Pass 1: Dead code deletion**
+   - **Pass 2: Duplicate removal**
+   - **Pass 3: Naming and error-handling cleanup**
+   - **Pass 4: Test reinforcement**
+   - Re-run targeted verification after each pass.
+   - Do not bundle unrelated refactors into the same edit set.
+
+5. **Run the quality gates**
+   - Keep regression tests green.
+   - Run the relevant lint, typecheck, and unit/integration tests for the touched area.
+   - Run existing static or security checks when available.
+   - If a gate fails, fix the issue or back out the risky cleanup instead of forcing it through.
+
+6. **Close with an evidence-dense report**
+   Always report:
+   - **Changed files**
+   - **Simplifications**
+   - **Behavior lock / verification run**
+   - **Remaining risks**
+
+## Usage
+
 - `/oh-my-copilot:ai-slop-cleaner <target>`
 - `/oh-my-copilot:ai-slop-cleaner <target> --review`
-</Usage>
+- `/oh-my-copilot:ai-slop-cleaner <file-a> <file-b> <file-c>`
+- From Ralph: run the cleaner on the Ralph session's changed files only, then return to Ralph for post-cleanup regression verification
+
+## Good Fits
+
+**Good:** `deslop this module: too many wrappers, duplicate helpers, and dead code`
+
+**Good:** `cleanup the AI slop in src/auth and tighten boundaries without changing behavior`
+
+**Bad:** `refactor auth to support SSO`
+
+**Bad:** `clean up formatting`

package/skills/ask/SKILL.md

@@ -1,22 +1,21 @@
 ---
 name: ask
-description: Process-first advisor routing for Copilot, Claude, Codex, or Gemini via `omcp ask`, with artifact capture and no raw CLI assembly
+description: Process-first advisor routing for Claude, Codex, or Gemini via `omc ask`, with artifact capture and no raw CLI assembly
 ---
 
 # Ask
 
-Use OMC's canonical advisor skill to route a prompt through a local CLI (Copilot, Claude, Codex, or Gemini) and persist the result as an ask artifact.
+Use OMC's canonical advisor skill to route a prompt through the local Claude, Codex, or Gemini CLI and persist the result as an ask artifact.
 
 ## Usage
 
 ```bash
-/oh-my-copilot:ask <copilot|claude|codex|gemini> <question or task>
+/oh-my-copilot:ask <claude|codex|gemini> <question or task>
 ```
 
 Examples:
 
 ```bash
-/oh-my-copilot:ask copilot "get a fresh perspective on this design decision"
 /oh-my-copilot:ask codex "review this patch from a security perspective"
 /oh-my-copilot:ask gemini "suggest UX improvements for this flow"
 /oh-my-copilot:ask claude "draft an implementation plan for issue #123"
@@ -27,10 +26,10 @@ Examples:
 **Required execution path — always use this command:**
 
 ```bash
-omcp ask {{ARGUMENTS}}
+omc ask {{ARGUMENTS}}
 ```
 
-**Do NOT manually construct raw provider CLI commands.** Never run `copilot`, `codex`, `claude`, or `gemini` directly to fulfill this skill. The `omcp ask` wrapper handles correct flag selection, artifact persistence, and provider-version compatibility automatically. Manually assembling provider CLI flags will produce incorrect or outdated invocations.
+**Do NOT manually construct raw provider CLI commands.** Never run `codex`, `claude`, or `gemini` directly to fulfill this skill. The `omc ask` wrapper handles correct flag selection, artifact persistence, and provider-version compatibility automatically. Manually assembling provider CLI flags will produce incorrect or outdated invocations.
 
 ## Requirements
 
@@ -38,7 +37,6 @@ omcp ask {{ARGUMENTS}}
 - Verify availability with the matching command:
 
 ```bash
-copilot --version
 claude --version
 codex --version
 gemini --version
@@ -46,7 +44,7 @@ gemini --version
 
 ## Artifacts
 
-`omcp ask` writes artifacts to:
+`omc ask` writes artifacts to:
 
 ```text
 .omcp/artifacts/ask/<provider>-<slug>-<timestamp>.md

package/skills/autopilot/SKILL.md

@@ -28,20 +28,6 @@ Autopilot takes a brief product idea and autonomously handles the full lifecycle
 Most non-trivial software tasks require coordinated phases: understanding requirements, designing a solution, implementing in parallel, testing, and validating quality. Autopilot orchestrates all of these phases automatically so the user can describe what they want and receive working code without managing each step.
 </Why_This_Exists>
 
-<Complexity_Gate>
-Before starting Phase 0, classify the task complexity:
-
-1. **Heuristic check** (zero-cost): The system's complexity classifier runs pattern matching on your prompt
-2. **AI assessment** (if heuristic inconclusive): Spawn an `explore` agent (haiku) to assess complexity
-
-**Routing by complexity:**
-- **SIMPLE** (e.g., "fix typo", "rename variable", "bump version"): Skip Phase 0 and Phase 1 entirely. Jump directly to Phase 2 (Execution) with a minimal plan.
-- **STANDARD** (default): Run the normal autopilot flow (all phases)
-- **COMPLEX** (e.g., auth systems, migrations, distributed architecture): Run all phases AND add Critic review after Phase 0 and Phase 1 for additional quality gates
-
-Complexity result is stored in `.omcp/state/sessions/{sessionId}/complexity.json` for downstream phases to reference.
-</Complexity_Gate>
-
 <Execution_Policy>
 - Each phase must complete before the next begins
 - Parallel execution is used within phases where possible (Phase 2 and Phase 4)
@@ -58,27 +44,23 @@ Complexity result is stored in `.omcp/state/sessions/{sessionId}/complexity.json
    - **If input is vague** (no file paths, function names, or concrete anchors): Offer redirect to `/deep-interview` for Socratic clarification before expanding
    - **Otherwise**: Analyst (Opus) extracts requirements, Architect (Opus) creates technical specification
    - Output: `.omcp/autopilot/spec.md`
-   - **Context capture**: Phase 0 output (spec summary) is captured for injection into Phase 1
 
 2. **Phase 1 - Planning**: Create an implementation plan from the spec
    - **If ralplan consensus plan exists**: Skip — already done in the 3-stage pipeline
    - Architect (Opus): Create plan (direct mode, no interview)
    - Critic (Opus): Validate plan
    - Output: `.omcp/plans/autopilot-impl.md`
-   - **Context capture**: Phase 1 output (plan summary) is captured for injection into Phase 2
 
 3. **Phase 2 - Execution**: Implement the plan using Ralph + Ultrawork
    - Executor (Haiku): Simple tasks
    - Executor (Sonnet): Standard tasks
    - Executor (Opus): Complex tasks
    - Run independent tasks in parallel
-   - **Context capture**: Phase 2 output (implementation summary: files changed, decisions made) is captured for injection into Phase 3
 
 4. **Phase 3 - QA**: Cycle until all tests pass (UltraQA mode)
    - Build, lint, test, fix failures
    - Repeat up to 5 cycles
    - Stop early if the same error repeats 3 times (indicates a fundamental issue)
-   - **Context capture**: Phase 3 output (QA results) is captured for injection into Phase 4
 
 5. **Phase 4 - Validation**: Multi-perspective review in parallel
    - Architect: Functional completeness
@@ -95,7 +77,7 @@ Complexity result is stored in `.omcp/state/sessions/{sessionId}/complexity.json
 - Use `Task(subagent_type="oh-my-copilot:architect", ...)` for Phase 4 architecture validation
 - Use `Task(subagent_type="oh-my-copilot:security-reviewer", ...)` for Phase 4 security review
 - Use `Task(subagent_type="oh-my-copilot:code-reviewer", ...)` for Phase 4 quality review
-- Agents form their own analysis first, then spawn Copilot Task agents for cross-validation
+- Agents form their own analysis first, then spawn Claude Task agents for cross-validation
 - Never block on external tools; proceed with available agents if delegation fails
 </Tool_Usage>
 
@@ -138,15 +120,6 @@ Why bad: This is an exploration/brainstorming request. Respond conversationally
 </Final_Checklist>
 
 <Advanced>
-## Context Accumulation
-
-Autopilot captures key outputs from each phase and injects them into the next phase's agent prompt as a `<prior-phase-context>` block. This ensures downstream agents have context from earlier phases without needing to re-read files.
-
-- Phase outputs are truncated to 12KB each
-- Context is session-scoped and cleared on `/cancel`
-- Includes: spec summaries, plan summaries, implementation decisions, QA results
-- Stored in `.omcp/state/sessions/{sessionId}/phase-context.json`
-
 ## Configuration
 
 Optional settings in `.copilot/omg.jsonc` (project) or `~/.config/copilot-omg/config.jsonc` (user):

package/skills/autoresearch/SKILL.md

@@ -12,14 +12,14 @@ Autoresearch is a stateful skill for bounded, evaluator-driven iterative improve
 <Use_When>
 - You already have a mission and evaluator from `/deep-interview --autoresearch`
 - You want persistent single-mission improvement with strict evaluation
-- You need durable experiment logs under `.omc/autoresearch/`
+- You need durable experiment logs under `.omcp/autoresearch/`
 - You want a supported path for periodic reruns via Claude Code native cron
 </Use_When>
 
 <Do_Not_Use_When>
 - You need evaluator generation at runtime — use `/deep-interview --autoresearch` first
 - You need multiple missions orchestrated together — v1 forbids that
-- You want the deprecated `omcp autoresearch` CLI flow — it is no longer authoritative
+- You want the deprecated `omc autoresearch` CLI flow — it is no longer authoritative
 </Do_Not_Use_When>
 
 <Contract>
@@ -31,7 +31,7 @@ Autoresearch is a stateful skill for bounded, evaluator-driven iterative improve
 </Contract>
 
 <Required_Artifacts>
-Canonical persistent storage lives under `.omc/autoresearch/<mission-slug>/` and/or `.omc/logs/autoresearch/<run-id>/`.
+Canonical persistent storage lives under `.omcp/autoresearch/<mission-slug>/` and/or `.omcp/logs/autoresearch/<run-id>/`.
 
 Minimum required artifacts:
 - mission spec
@@ -41,7 +41,7 @@ Minimum required artifacts:
 
 Recommended canonical shape:
 ```text
-.omc/autoresearch/<mission-slug>/
+.omcp/autoresearch/<mission-slug>/
   mission.md
   evaluator.json
   runs/<run-id>/
@@ -83,7 +83,7 @@ If cron is used:
 </Cron_Integration>
 
 <Execution_Policy>
-- Do not hand execution back to `omcp autoresearch`
+- Do not hand execution back to `omc autoresearch`
 - Do not create multi-mission orchestration
 - Prefer reusing `src/autoresearch/*` runtime/schema helpers where they already match the stricter contract
 - Keep logs useful to humans, not only machines

package/skills/cancel/SKILL.md

@@ -39,7 +39,7 @@ Or say: "cancelomc", "stopomc"
 ## Critical: Deferred Tool Handling
 
 The state management tools (`state_clear`, `state_read`, `state_write`, `state_list_active`,
-`state_get_status`) may be registered as **deferred tools** by Copilot CLI. Before calling
+`state_get_status`) may be registered as **deferred tools** by Claude Code. Before calling
 any state tool, you MUST first load all of them via `ToolSearch`:
 
 ```
@@ -115,10 +115,10 @@ Active modes are still cancelled in dependency order:
 5. Swarm (standalone)
 6. Ultrapilot (standalone)
 7. Pipeline (standalone)
-8. Team (Copilot CLI native)
+8. Team (Claude Code native)
 9. OMC Teams (tmux CLI workers)
 10. Plan Consensus (standalone)
-11. Self-Improve (standalone — clear state, clean orphaned worktrees, preserve iteration_state for resume, set status: "user_stopped" in the resolved `<self-improve-root>/state/agent-settings.json`; new runs use `.omc/self-improve/topics/<topic-slug>/`, with flat `.omc/self-improve/` retained only for legacy single-track resumes)
+11. Self-Improve (standalone — clear state, clean orphaned worktrees, preserve iteration_state for resume, set status: "user_stopped" in the resolved `<self-improve-root>/state/agent-settings.json`; new runs use `.omcp/self-improve/topics/<topic-slug>/`, with flat `.omcp/self-improve/` retained only for legacy single-track resumes)
 
 ## Force Clear All
 
@@ -136,7 +136,7 @@ Steps under the hood:
 1. `state_list_active` enumerates `.omcp/state/sessions/{sessionId}/…` to find every known session.
 2. `state_clear` runs once per session to drop that session’s files.
 3. A global `state_clear` without `session_id` removes legacy files under `.omcp/state/*.json`, `.omcp/state/swarm*.db`, and compatibility artifacts (see list).
-4. Team artifacts (`~/.copilot/teams/*/`, `~/.copilot/tasks/*/`, `.omcp/state/team-state.json`) are best-effort cleared as part of the legacy fallback.
+4. Team artifacts (`~/.claude/teams/*/`, `~/.claude/tasks/*/`, `.omcp/state/team-state.json`) are best-effort cleared as part of the legacy fallback.
    - Cancel for native team does NOT affect omc-teams state, and vice versa.
 
 Every `state_clear` command honors the `session_id` argument, so even force mode still uses the session-aware paths first before deleting legacy files.
@@ -196,7 +196,7 @@ Use force mode to clear every session plus legacy artifacts via `state_clear`. D
 
 ### 3B. Smart Cancellation (default)
 
-#### If Team Active (Copilot CLI native)
+#### If Team Active (Claude Code native)
 
 Teams are detected by checking for config files in `${COPILOT_CONFIG_DIR:-~/.copilot}/teams/`:
 
@@ -233,7 +233,7 @@ After graceful pass:
 
 **TeamDelete + Cleanup:**
 ```
-  1. Call TeamDelete() — removes ~/.copilot/teams/{name}/ and ~/.copilot/tasks/{name}/
+  1. Call TeamDelete() — removes ~/.claude/teams/{name}/ and ~/.claude/tasks/{name}/
   2. Clear team state: state_clear(mode="team")
   3. Check for linked ralph: state_read(mode="ralph") — if linked_team is true:
      a. Clear ralph state: state_clear(mode="ralph")
@@ -246,7 +246,7 @@ After graceful pass:
 
 After TeamDelete, verify no agent processes remain:
 ```bash
-node "${PLUGIN_ROOT}/scripts/cleanup-orphans.mjs" --team-name "{team_name}"
+node "${CLAUDE_PLUGIN_ROOT}/scripts/cleanup-orphans.mjs" --team-name "{team_name}"
 ```
 
 The orphan scanner:
@@ -264,7 +264,7 @@ Team "{team_name}" cancelled:
   - Unresponsive: K (list names if any)
   - TeamDelete: success/failed
   - Manual cleanup needed: yes/no
-    Path: ~/.copilot/teams/{name}/ and ~/.copilot/tasks/{name}/
+    Path: ~/.claude/teams/{name}/ and ~/.claude/tasks/{name}/
 ```
 
 **Implementation note:** The cancel skill is executed by the LLM, not as a bash script. When you detect an active team:
@@ -318,7 +318,7 @@ The cancel skill runs as follows:
 2. Use `state_list_active` to enumerate known session ids and `state_get_status` to learn the active mode (`autopilot`, `ralph`, `ultrawork`, etc.) for each session.
 3. When operating in default mode, call `state_clear` with that session_id to remove only the session’s files, then run mode-specific cleanup (autopilot → ralph → …) based on the state tool signals.
 4. In force mode, iterate every active session, call `state_clear` per session, then run a global `state_clear` without `session_id` to drop legacy files (`.omcp/state/*.json`, compatibility artifacts) and report success. Swarm remains a shared SQLite/marker mode outside session scoping.
-5. Team artifacts (`~/.copilot/teams/*/`, `~/.copilot/tasks/*/`, `.omcp/state/team-state.json`) remain best-effort cleanup items invoked during the legacy/global pass.
+5. Team artifacts (`~/.claude/teams/*/`, `~/.claude/tasks/*/`, `.omcp/state/team-state.json`) remain best-effort cleanup items invoked during the legacy/global pass.
 6. **Always** clear skill-active state as the final step, regardless of which mode was active or whether `--force` was used:
    ```
    state_clear(mode="skill-active", session_id)
@@ -364,7 +364,7 @@ Mode-specific subsections below describe what extra cleanup each handler perform
 - **Safe**: Only clears linked Ultrawork, preserves standalone Ultrawork
 - **Local-only**: Clears state files in `.omcp/state/` directory
 - **Resume-friendly**: Autopilot state is preserved for seamless resume
-- **Team-aware**: Detects native Copilot CLI teams and performs graceful shutdown
+- **Team-aware**: Detects native Claude Code teams and performs graceful shutdown
 
 ## MCP Worker Cleanup
 
@@ -372,7 +372,7 @@ When cancelling modes that may have spawned MCP workers (team bridge daemons), t
 
 1. **Check for active MCP workers**: Look for heartbeat files at `.omcp/state/team-bridge/{team}/*.heartbeat.json`
 2. **Send shutdown signals**: Write shutdown signal files for each active worker
-3. **Kill tmux sessions**: Run `tmux kill-session -t omcp-team-{team}-{worker}` for each worker
+3. **Kill tmux sessions**: Run `tmux kill-session -t omc-team-{team}-{worker}` for each worker
 4. **Clean up heartbeat files**: Remove all heartbeat files for the team
 5. **Clean up shadow registry**: Remove `.omcp/state/team-mcp-workers.json`
 
@@ -382,6 +382,6 @@ When `--force` is used, also clean up:
 ```bash
 rm -rf .omcp/state/team-bridge/       # Heartbeat files
 rm -f .omcp/state/team-mcp-workers.json  # Shadow registry
-# Kill all omcp-team-* tmux sessions
-tmux list-sessions -F '#{session_name}' 2>/dev/null | grep '^omcp-team-' | while read s; do tmux kill-session -t "$s" 2>/dev/null; done
+# Kill all omc-team-* tmux sessions
+tmux list-sessions -F '#{session_name}' 2>/dev/null | grep '^omc-team-' | while read s; do tmux kill-session -t "$s" 2>/dev/null; done
 ```

package/skills/cccg/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: cccg
 description: Quadri-model orchestration — Copilot, Claude, Codex, and Gemini each provide independent analysis, then Copilot synthesizes
+level: 5
 ---
 
 # CCCG - Copilot-Claude-Codex-Gemini Orchestration