codymaster 5.2.0 → 7.0.0

package/skills/cm-autopilot/scripts/autopilot.py

@@ -15,9 +15,26 @@ import subprocess
 import threading
 from pathlib import Path
 
-# Add cm-content-factory to sys.path to reuse the dispatcher and state manager
+# Reuse dispatcher and state manager from the content-factory plugin.
+# After the 2026-05-09 plugin split, content-factory lives in a separate plugin.
+# Resolution order: env override → sibling extracted-plugins (dev) → installed plugin paths.
 SKILLS_DIR = Path(__file__).resolve().parent.parent.parent
-CF_SCRIPTS = SKILLS_DIR / "cm-content-factory" / "scripts"
+REPO_ROOT = SKILLS_DIR.parent
+
+def _find_cf_scripts() -> Path:
+    env = os.environ.get("CONTENT_FACTORY_SCRIPTS")
+    if env and Path(env).exists():
+        return Path(env)
+    candidates = [
+        REPO_ROOT / "extracted-plugins" / "content-factory" / "skills" / "content-factory" / "scripts",
+        Path.home() / ".claude" / "plugins" / "cache" / "content-factory" / "skills" / "content-factory" / "scripts",
+    ]
+    for c in candidates:
+        if c.exists():
+            return c
+    return SKILLS_DIR / "cm-content-factory" / "scripts"  # legacy fallback
+
+CF_SCRIPTS = _find_cf_scripts()
 sys.path.append(str(CF_SCRIPTS))
 
 try:

package/skills/cm-brainstorm-idea/SKILL.md

@@ -1,10 +1,19 @@
 ---
 name: cm-brainstorm-idea
 description: "Strategic analysis gate for existing products — multi-dimensional evaluation (tech, product, design, business) using Design Thinking + 9 Windows (TRIZ) + Double Diamond. Outputs 2-3 qualified options with recommendations. Use BEFORE cm-planning for complex initiatives and enhancements on existing codebases."
+token_budget: 1500
+compressed: true
+deprecated: false
 ---
 
 # Brainstorm Idea — Strategic Analysis Gate
 
+## TL;DR
+- **Use before** cm-planning for complex/ambiguous initiatives
+- **Frameworks**: Design Thinking + 9 Windows (TRIZ) + Double Diamond
+- **Output**: 2-3 qualified options + recommendation
+- **Writes**: handoff/intent.json
+
 > **Understand deeply. Evaluate multi-dimensionally. Propose qualified options. Then — and only then — plan.**
 > This skill is the BRIDGE between an existing product and its next evolution.
 

package/skills/cm-clean-code/SKILL.md

@@ -1,10 +1,19 @@
 ---
 name: cm-clean-code
 description: "Code hygiene gate — detect and eliminate dead code, duplicates, naming mess, and code smells. TRIZ-powered. Run after features, before PRs, during debt sprints."
+token_budget: 1200
+compressed: true
+deprecated: false
 ---
 
 # Clean Code — Code Hygiene Gate
 
+## TL;DR
+- **Use after** a feature lands, before PR review
+- **Detects**: dead code, duplicates, naming smells, dependency drift
+- **Powered by** TRIZ contradictions and Boy Scout rule
+- **Next**: cm-code-review
+
 > **Code that works is not enough. Code must be CLEAN.**
 > Inspired by Clean Code (Robert C. Martin) + Refactoring (Martin Fowler) + TRIZ.
 
@@ -295,6 +304,17 @@ cm-execution → cm-clean-code → cm-code-review → cm-quality-gate → cm-saf
    (build)      (hygiene)        (review)          (verify)         (ship)
 ```
 
+## Karpathy Discipline — Simplicity First
+
+Combat over-engineering at the source, not after the fact:
+- **No features beyond what was asked.** No "while I'm here" additions.
+- **No abstractions for single-use code.** Three similar lines beats a premature interface.
+- **No flexibility/configurability that wasn't requested.** YAGNI is the default.
+- **No error handling for impossible scenarios.** Trust internal callers; validate at boundaries.
+- **200 lines that should be 50 → rewrite, don't ship.**
+
+**Senior-engineer test:** "Would a senior call this overcomplicated?" If yes, simplify before commit.
+
 ## The Bottom Line
 
 **Clean code = investment. Dirty code = debt. Pay as you go, or pay with interest later.**

package/skills/cm-code-review/SKILL.md

@@ -1,10 +1,20 @@
 ---
 name: cm-code-review
 description: "Full review lifecycle — request reviews, handle feedback with technical rigor, and complete branch integration. Use when completing tasks, receiving feedback, or finishing feature branches."
+token_budget: 1500
+compressed: true
+deprecated: false
 ---
 
 # Code Review — Request + Receive + Complete
 
+## TL;DR
+- **Use when** task complete, before/during PR review
+- **Pre-review**: lint, tests, diff scan, blast radius
+- **Reads**: handoff/exec.json — **Writes**: handoff/review.json
+- **Severity**: info | warn | error | critical
+- **Next**: cm-quality-gate
+
 > **Full review lifecycle in one skill:** Request → Receive → Integrate.
 
 ## Part A: Requesting Code Review
@@ -146,6 +156,17 @@ After processing review feedback, ALWAYS update `.cm/CONTINUITY.md`:
 | `cm-identity-guard` | Before git push |
 | `cm-git-worktrees` | Cleanup worktree after completion |
 
+## Karpathy Discipline — Review Checklist
+
+Block any PR/diff that violates these regardless of green tests:
+- **Scope creep:** changed line that doesn't trace to the task → request removal.
+- **Bloat:** new abstraction with one caller, premature config, error paths for impossible inputs → request simplification.
+- **Side-effect edits:** unrelated formatting, renamed identifiers, "improved" comments not in scope → revert.
+- **Hidden assumptions:** logic that depends on an unstated invariant → require it surfaced (test or doc) or rejected.
+- **Weak goals:** PR description says "make it work" with no verifiable criterion → send back to planning.
+
+**Review heuristic:** if you can't answer "what task forced this line?" for every changed line, the diff is too wide.
+
 ## The Bottom Line
 
 **Review early. Verify feedback. Ship with evidence, not hope.**

package/skills/cm-codeintell/SKILL.md

@@ -1,10 +1,19 @@
 ---
 name: cm-codeintell
 description: "Unified code intelligence — Skeleton Index (zero-dep, <4s) + AST knowledge graph (CodeGraph) + architecture diagrams (Mermaid) + smart context builder. Pre-indexes code structure so AI agents understand any codebase instantly. 95% token compression for onboarding. 30% fewer tokens for deep analysis."
+token_budget: 1500
+compressed: true
+deprecated: false
 ---
 
 # Code Intelligence — Structural Understanding for AI Agents
 
+## TL;DR
+- **Use to** index codebase for fast structural understanding
+- **Outputs**: skeleton index, AST graph, Mermaid diagrams
+- **Token saving**: ~95% for onboarding, ~30% for deep analysis
+- **Next**: cm-planning or cm-debugging
+
 > **Stop scanning. Start querying.** Skeleton Index (<4s, zero deps) + AST graph + architecture diagrams = instant code understanding.
 > Inspired by [CodeGraph](https://github.com/colbymchenry/codegraph) + [GitDiagram](https://github.com/ahmedkhaleel2004/gitdiagram).
 > TRIZ-optimized: 10 inventive principles applied.

package/skills/cm-conductor-worktrees/SKILL.archive.md

@@ -0,0 +1,28 @@
+---
+name: cm-conductor-worktrees
+description: "Use when you need to manage parallel git worktrees for isolated feature development."
+---
+# cm-conductor-worktrees — parallel worktrees
+
+## CLI
+
+```bash
+cm conductor add --at ../my-feature-wt --branch feat/my-feature --base main
+cm conductor list
+```
+
+## Practice
+
+- One **branch + worktree** per parallel agent/session.
+- Reconcile with `git merge` / PR; avoid two agents editing the same files without coordination.
+
+## ELI16 (3+ sessions)
+
+When running **three or more** parallel sessions, re-ground each session with:
+
+- Current branch name + worktree path.
+- Last artifact from `cm sprint status` or `.cm/context-bus.json`.
+
+## Future
+
+Dashboard UI for active sprints is **not** in CLI yet — use `cm dashboard` / Hamster UI where available.

package/skills/cm-conductor-worktrees/SKILL.md

@@ -1,28 +1,26 @@
 ---
 name: cm-conductor-worktrees
-description: "Use when you need to manage parallel git worktrees for isolated feature development."
+description: "[Deprecated] parallel execution mode. Use `cm-execution` instead."
+deprecated: true
+merged_into: cm-execution
 ---
-# cm-conductor-worktrees — parallel worktrees
 
-## CLI
+# cm-conductor-worktrees — Deprecated
 
-```bash
-cm conductor add --at ../my-feature-wt --branch feat/my-feature --base main
-cm conductor list
-```
-
-## Practice
-
-- One **branch + worktree** per parallel agent/session.
-- Reconcile with `git merge` / PR; avoid two agents editing the same files without coordination.
+> ⚠️ This skill is deprecated as of CodyMaster v6.0.0 and will be removed in v6.1.0.
+>
+> **Use `cm-execution` instead.** parallel execution mode.
+>
+> See [docs/migration-v2.md](../../docs/migration-v2.md) for the full mapping.
 
-## ELI16 (3+ sessions)
+The original content is preserved at [SKILL.archive.md](SKILL.archive.md) for reference.
 
-When running **three or more** parallel sessions, re-ground each session with:
+## Migration
 
-- Current branch name + worktree path.
-- Last artifact from `cm sprint status` or `.cm/context-bus.json`.
-
-## Future
+```bash
+# Old:           cm <use this skill>
+# New (v6.0+):   cm execution <equivalent action>
+```
 
-Dashboard UI for active sprints is **not** in CLI yet — use `cm dashboard` / Hamster UI where available.
+If you depend on a capability that didn't carry over, please file an issue:
+https://github.com/tody-agent/codymaster/issues

package/skills/cm-continuity/SKILL.md

@@ -1,10 +1,19 @@
 ---
 name: cm-continuity
 description: "Working memory protocol — maintains context across sessions via CONTINUITY.md. Inspired by Loki Mode. Read at turn start, update at turn end. Captures mistakes and learnings to prevent repeating errors."
+token_budget: 1200
+compressed: true
+deprecated: false
 ---
 
 # Continuity — Working Memory Protocol
 
+## TL;DR
+- **Use at** session start (read) and end (update)
+- **File**: .cm/CONTINUITY.md (working memory)
+- **Auto-loads**: recent learnings from .cm/learnings.jsonl
+- **Loki Mode**: prevents repeating past mistakes
+
 > **Context persistence across sessions. Mistakes captured. Learnings applied.**
 > Inspired by Loki Mode's CONTINUITY.md protocol (Autonomi).
 

package/skills/cm-dashboard/SKILL.archive.md

@@ -0,0 +1,15 @@
+---
+name: cm-dashboard
+description: Open visual Dashboard to track work status (Simulated Kanban board)
+---
+
+# Command: `/cm-dashboard`
+
+When this command is called, the AI Assistant should:
+
+1. **Check status:** Find and read the OpenSpec `openspec/changes/[init]/tasks.md` (and synced `cm-tasks.json`) file in the current project directory (or artifacts directory).
+2. **Visual display:** Aggregate tasks and render them as a Kanban board (Markdown table) with 3 columns:
+   - **🔴 TO DO** (Not started)
+   - **🟡 IN PROGRESS** (In progress)
+   - **🟢 DONE** (Completed)
+3. **Flow report:** Briefly summarize which Mode the Agent is in (PLANNING, EXECUTION, or VERIFICATION) and what the Next Step is.

package/skills/cm-dashboard/SKILL.md

@@ -1,15 +1,26 @@
 ---
 name: cm-dashboard
-description: Open visual Dashboard to track work status (Simulated Kanban board)
+description: "[Deprecated] both visualize project state. Use `cm-status` instead."
+deprecated: true
+merged_into: cm-status
 ---
 
-# Command: `/cm-dashboard`
+# cm-dashboard — Deprecated
 
-When this command is called, the AI Assistant should:
+> ⚠️ This skill is deprecated as of CodyMaster v6.0.0 and will be removed in v6.1.0.
+>
+> **Use `cm-status` instead.** both visualize project state.
+>
+> See [docs/migration-v2.md](../../docs/migration-v2.md) for the full mapping.
 
-1. **Check status:** Find and read the OpenSpec `openspec/changes/[init]/tasks.md` (and synced `cm-tasks.json`) file in the current project directory (or artifacts directory).
-2. **Visual display:** Aggregate tasks and render them as a Kanban board (Markdown table) with 3 columns:
-   - **🔴 TO DO** (Not started)
-   - **🟡 IN PROGRESS** (In progress)
-   - **🟢 DONE** (Completed)
-3. **Flow report:** Briefly summarize which Mode the Agent is in (PLANNING, EXECUTION, or VERIFICATION) and what the Next Step is.
+The original content is preserved at [SKILL.archive.md](SKILL.archive.md) for reference.
+
+## Migration
+
+```bash
+# Old:           cm <use this skill>
+# New (v6.0+):   cm status <equivalent action>
+```
+
+If you depend on a capability that didn't carry over, please file an issue:
+https://github.com/tody-agent/codymaster/issues

package/skills/cm-dashboard/ui/app.js

@@ -926,7 +926,15 @@
   }
 
   // ── Utilities ──────────────────────────────
-  function esc(str) { const d = document.createElement('div'); d.textContent = str; return d.innerHTML; }
+  function esc(str) {
+    if (str == null) return '';
+    return String(str)
+      .replace(/&/g, '&')
+      .replace(/</g, '&lt;')
+      .replace(/>/g, '&gt;')
+      .replace(/"/g, '&quot;')
+      .replace(/'/g, '&#39;');
+  }
   function formatTimeAgo(dateStr) {
     const ms = Date.now() - new Date(dateStr).getTime();
     const m = Math.floor(ms / 60000), h = Math.floor(ms / 3600000), d = Math.floor(ms / 86400000);

package/skills/cm-debugging/SKILL.md

@@ -1,10 +1,19 @@
 ---
 name: cm-debugging
 description: Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
+token_budget: 1500
+compressed: true
+deprecated: false
 ---
 
 # Systematic Debugging
 
+## TL;DR
+- **Use when** any bug, test failure, or unexpected behavior surfaces
+- **Process**: reproduce → isolate → diagnose root cause → fix
+- **Defense in depth**: also add a test that locks the bug
+- **Next**: cm-tdd → cm-quality-gate
+
 ## Overview
 
 Random fixes waste time and create new bugs. Quick patches mask underlying issues.

package/skills/cm-design-studio/SKILL.archive.md

@@ -0,0 +1,34 @@
+---
+name: cm-design-studio
+description: "Use when you need to create 2-3 UI/UX design variants and document a repeatable handoff before coding."
+---
+# cm-design-studio
+
+> Local design-variant workspace: checklist, named variants, and a handoff stub—no external MCP required.
+
+## When to use
+
+- You want **2–3 UI/UX variants** documented before coding.
+- You need a **repeatable handoff** from design choice to implementation agents.
+- You prefer **files under `.cm/`** over ad-hoc chat-only decisions.
+
+## Steps
+
+1. From the repo root: `cm design-studio init`
+2. Edit `.cm/design-studio/CHECKLIST.md` and `VARIANTS.md` (name options A/B/C).
+3. Pick a variant; complete `.cm/design-studio/HANDOFF.md` (screens, tokens, prompt stub).
+4. Run implementation skills (e.g. `cm-execution`, `cm-tdd`) **using the HANDOFF prompt stub** as the single source of truth.
+
+Optional: `cm design-studio status` — list artifact files.
+
+## Output
+
+- `.cm/design-studio/README.md` — happy path
+- `.cm/design-studio/CHECKLIST.md`
+- `.cm/design-studio/VARIANTS.md`
+- `.cm/design-studio/HANDOFF.md`
+
+## Related
+
+- ADR 003 (`docs/adr/003-skill-distro-and-meta.md`) for pack layout when publishing skills.
+- `cm suggest` may recommend other skills based on git + sprint state.

package/skills/cm-design-studio/SKILL.md

@@ -1,34 +1,26 @@
 ---
 name: cm-design-studio
-description: "Use when you need to create 2-3 UI/UX design variants and document a repeatable handoff before coding."
+description: "[Deprecated] design pipeline merged. Use `cm-design-system` instead."
+deprecated: true
+merged_into: cm-design-system
 ---
-# cm-design-studio
 
-> Local design-variant workspace: checklist, named variants, and a handoff stub—no external MCP required.
+# cm-design-studio — Deprecated
 
-## When to use
+> ⚠️ This skill is deprecated as of CodyMaster v6.0.0 and will be removed in v6.1.0.
+>
+> **Use `cm-design-system` instead.** design pipeline merged.
+>
+> See [docs/migration-v2.md](../../docs/migration-v2.md) for the full mapping.
 
-- You want **2–3 UI/UX variants** documented before coding.
-- You need a **repeatable handoff** from design choice to implementation agents.
-- You prefer **files under `.cm/`** over ad-hoc chat-only decisions.
+The original content is preserved at [SKILL.archive.md](SKILL.archive.md) for reference.
 
-## Steps
+## Migration
 
-1. From the repo root: `cm design-studio init`
-2. Edit `.cm/design-studio/CHECKLIST.md` and `VARIANTS.md` (name options A/B/C).
-3. Pick a variant; complete `.cm/design-studio/HANDOFF.md` (screens, tokens, prompt stub).
-4. Run implementation skills (e.g. `cm-execution`, `cm-tdd`) **using the HANDOFF prompt stub** as the single source of truth.
+```bash
+# Old:           cm <use this skill>
+# New (v6.0+):   cm design-system <equivalent action>
+```
 
-Optional: `cm design-studio status` — list artifact files.
-
-## Output
-
-- `.cm/design-studio/README.md` — happy path
-- `.cm/design-studio/CHECKLIST.md`
-- `.cm/design-studio/VARIANTS.md`
-- `.cm/design-studio/HANDOFF.md`
-
-## Related
-
-- ADR 003 (`docs/adr/003-skill-distro-and-meta.md`) for pack layout when publishing skills.
-- `cm suggest` may recommend other skills based on git + sprint state.
+If you depend on a capability that didn't carry over, please file an issue:
+https://github.com/tody-agent/codymaster/issues

package/skills/cm-design-system/SKILL.md

@@ -10,6 +10,7 @@ description: |
 Establish a robust, stable, and consistent UI Design System by either extracting tokens from an existing source (Harvester mode) or scaffolding a fresh system based on premium Kits (Shadcn, Halo, Lunaris, Nitro). Output a strictly formatted `DESIGN.md` artifact ready for UI generation.
 
 # Instructions
+0. **Load Design Taste** (if `.cm/design-taste.json` exists): Before proposing tokens, call `topTaste(cwd, 'color')`, `topTaste(cwd, 'font')`, `topTaste(cwd, 'layout')` from `src/utils/design-taste.ts`. Bias selections toward `approved` entries; avoid `rejected`. Decay is 5 %/week so stale taste fades — trust live weights. After the user accepts or rejects a palette, call `recordTaste(cwd, { dimension, value, verdict })` so future runs improve.
 1. **Clarify Intent**: Determine if the user wants to *extract* an existing design from a URL/Image or *create* a new system from a specific UI Kit.
 2. **Harvester Extraction (If applicable)**: 
    - Analyze the target visual source.

package/skills/cm-engineering-meta/SKILL.archive.md

@@ -0,0 +1,73 @@
+---
+name: cm-engineering-meta
+description: "Use when looking up quick wins, access patterns, or voice map for the engineering meta layer."
+---
+# cm-engineering-meta — quick wins + access + voice map
+
+## Search before building
+
+Before adding infrastructure, search in three layers:
+
+1. **Tried-and-true** — patterns already in this repo / sibling services.
+2. **New-and-popular** — current docs for your stack version.
+3. **First-principles** — only when 1–2 don’t apply.
+
+## AskUserQuestion format
+
+When asking the human to choose:
+
+- Short **context** (what you already know).
+- Clear **question**.
+- **RECOMMENDATION** (one option you’d pick and why).
+- Lettered options **A / B / C** (not vague yes/no).
+
+## Review readiness dashboard (ASCII)
+
+Before ship, print a table:
+
+```
+| Gate        | Status | Notes |
+|-------------|--------|-------|
+| Tests       | ?      |       |
+| Lint/Type   | ?      |       |
+| Secrets     | ?      |       |
+| Manual QA   | ?      |       |
+```
+
+## Completeness gap (code review)
+
+Flag when an **80% solution** is chosen but the **100%** path costs **< 30 minutes** (tests, edge case, docs).
+
+## Investigate Iron Law
+
+- Do **not** patch without a **root cause** hypothesis.
+- After **three** failed fix attempts, stop and question architecture or gather more data.
+
+## Access controls (Goose-style)
+
+- Maintain lists: **autonomous_ok** vs **confirm_required** skill groups (see `.cm/config.example.yaml`).
+- Respect “stop suggesting skill X” in session notes.
+
+## Provider abstraction
+
+Prefer interfaces for LLM calls so **cm-second-opinion** can swap `OPENAI_API_KEY` / future providers without rewriting skills.
+
+## Proactive skill suggestion
+
+Infer stage from files touched and git state:
+
+- Many `test/` edits → suggest **cm-test-gate**.
+- `Dockerfile` / deploy scripts → **cm-safe-deploy** + **cm canary**.
+- `rm` / migration scripts → **cm-guardian** + **cm-secret-shield**.
+
+## Voice-friendly triggers (examples)
+
+| Phrase (approx.) | Skill / command |
+|------------------|-----------------|
+| “Run a security check” | cm-secret-shield / cm-security-gate |
+| “Test the website” | cm browse + cm qa-visual |
+| “Code review this” | cm-code-review |
+| “Deploy safely” | cm-safe-deploy |
+| “Log what went wrong” | `cm retro --note "…"` |
+
+Use Whisper / AquaVoice → paste transcript; map keywords to the table above.

package/skills/cm-engineering-meta/SKILL.md

@@ -1,73 +1,26 @@
 ---
 name: cm-engineering-meta
-description: "Use when looking up quick wins, access patterns, or voice map for the engineering meta layer."
+description: "[Deprecated] engineering bridge merged. Use `cm-mcp-engineering` instead."
+deprecated: true
+merged_into: cm-mcp-engineering
 ---
-# cm-engineering-meta — quick wins + access + voice map
 
-## Search before building
+# cm-engineering-meta — Deprecated
 
-Before adding infrastructure, search in three layers:
+> ⚠️ This skill is deprecated as of CodyMaster v6.0.0 and will be removed in v6.1.0.
+>
+> **Use `cm-mcp-engineering` instead.** engineering bridge merged.
+>
+> See [docs/migration-v2.md](../../docs/migration-v2.md) for the full mapping.
 
-1. **Tried-and-true** — patterns already in this repo / sibling services.
-2. **New-and-popular** — current docs for your stack version.
-3. **First-principles** — only when 1–2 don’t apply.
+The original content is preserved at [SKILL.archive.md](SKILL.archive.md) for reference.
 
-## AskUserQuestion format
+## Migration
 
-When asking the human to choose:
-
-- Short **context** (what you already know).
-- Clear **question**.
-- **RECOMMENDATION** (one option you’d pick and why).
-- Lettered options **A / B / C** (not vague yes/no).
-
-## Review readiness dashboard (ASCII)
-
-Before ship, print a table:
-
-```
-| Gate        | Status | Notes |
-|-------------|--------|-------|
-| Tests       | ?      |       |
-| Lint/Type   | ?      |       |
-| Secrets     | ?      |       |
-| Manual QA   | ?      |       |
+```bash
+# Old:           cm <use this skill>
+# New (v6.0+):   cm mcp-engineering <equivalent action>
 ```
 
-## Completeness gap (code review)
-
-Flag when an **80% solution** is chosen but the **100%** path costs **< 30 minutes** (tests, edge case, docs).
-
-## Investigate Iron Law
-
-- Do **not** patch without a **root cause** hypothesis.
-- After **three** failed fix attempts, stop and question architecture or gather more data.
-
-## Access controls (Goose-style)
-
-- Maintain lists: **autonomous_ok** vs **confirm_required** skill groups (see `.cm/config.example.yaml`).
-- Respect “stop suggesting skill X” in session notes.
-
-## Provider abstraction
-
-Prefer interfaces for LLM calls so **cm-second-opinion** can swap `OPENAI_API_KEY` / future providers without rewriting skills.
-
-## Proactive skill suggestion
-
-Infer stage from files touched and git state:
-
-- Many `test/` edits → suggest **cm-test-gate**.
-- `Dockerfile` / deploy scripts → **cm-safe-deploy** + **cm canary**.
-- `rm` / migration scripts → **cm-guardian** + **cm-secret-shield**.
-
-## Voice-friendly triggers (examples)
-
-| Phrase (approx.) | Skill / command |
-|------------------|-----------------|
-| “Run a security check” | cm-secret-shield / cm-security-gate |
-| “Test the website” | cm browse + cm qa-visual |
-| “Code review this” | cm-code-review |
-| “Deploy safely” | cm-safe-deploy |
-| “Log what went wrong” | `cm retro --note "…"` |
-
-Use Whisper / AquaVoice → paste transcript; map keywords to the table above.
+If you depend on a capability that didn't carry over, please file an issue:
+https://github.com/tody-agent/codymaster/issues