codymaster 4.8.0 → 7.0.0

package/skills/cm-skill-health/SKILL.archive.md

@@ -0,0 +1,83 @@
+---
+name: cm-skill-health
+description: "Operational health review for CodyMaster skills using current repo signals: validate-skills, suggest, retro logs, memory, and test gates."
+---
+
+# cm-skill-health
+
+Use this skill when a CodyMaster skill feels stale, misleading, unreliable, or under-documented.
+
+## What it checks
+
+1. Discovery drift
+   - Is the skill present in `skills/`, docs indexes, profiles, and README surfaces?
+2. Invocation friction
+   - Does `cm suggest` point users to the skill when the task matches?
+3. Operational evidence
+   - Are there recurring failures or learnings in `.cm/operational-learnings.jsonl`?
+4. Contract health
+   - Does the skill reference commands, files, or paths that still exist?
+5. Release safety
+   - Does the repo still pass `npm run validate:skills`, `npm run check:skills`, and the test gate?
+
+## Workflow
+
+1. Confirm the symptom.
+   - Missing from docs
+   - Missing from profiles
+   - Broken references inside `SKILL.md`
+   - Repeated runtime pain in retro notes
+2. Compare the live skill against:
+   - `docs/skills/index.md`
+   - `skills/profiles/full.txt`
+   - `README.md`
+   - related changelog promises
+3. Scan evidence sources.
+   - `cm advisory handoff --for cm-skill-health`
+   - `cm suggest --project .`
+   - `cm retro summary --project .`
+   - `.cm/CONTINUITY.md`
+   - `rg` over `skills/`, `docs/`, and `src/`
+4. Score the issue.
+   - `healthy`: discoverable, accurate, references valid
+   - `degraded`: present but misleading or inconsistent
+   - `broken`: missing, invalid, or unusable
+5. Hand off to:
+   - `cm-skill-evolution` to repair or derive the next version
+
+## Output
+
+Produce a short health note:
+
+```md
+## Skill Health
+- Skill: cm-...
+- Status: healthy | degraded | broken
+- Symptoms: ...
+- Evidence: ...
+- Recovery path: FIX | DERIVED | CAPTURED
+```
+
+Preferred input contract:
+
+```md
+## Advisory Handoff
+- Consumer: cm-skill-health
+- Skill: cm-...
+- Recovery path: FIX | DERIVED | CAPTURED | NONE
+- Confidence: 0.xx
+- Source analysis: EA-...
+- Task: ...
+- Status: completed | partial | failed
+- Evidence: ...
+- Selected skills: ...
+- Target skills: ...
+- Quality weight: 0.xx
+- Next step: ...
+```
+
+## Red flags
+
+- Do not claim metric dashboards or automatic scoring unless the repo actually implements them.
+- Do not treat README marketing copy as proof that a skill exists.
+- Do not evolve the skill before identifying whether the problem is docs drift, packaging drift, or missing implementation.

package/skills/cm-skill-health/SKILL.md

@@ -0,0 +1,26 @@
+---
+name: cm-skill-health
+description: "[Deprecated] skill lifecycle merged. Use `cm-skill-evolution` instead."
+deprecated: true
+merged_into: cm-skill-evolution
+---
+
+# cm-skill-health — Deprecated
+
+> ⚠️ This skill is deprecated as of CodyMaster v6.0.0 and will be removed in v6.1.0.
+>
+> **Use `cm-skill-evolution` instead.** skill lifecycle merged.
+>
+> See [docs/migration-v2.md](../../docs/migration-v2.md) for the full mapping.
+
+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 skill-evolution <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-skill-index/SKILL.md

@@ -1,10 +1,18 @@
 ---
 name: cm-skill-index
 description: "Progressive Disclosure skill index — efficient skill loading in 3 layers. Layer 1 (index, ~100 tokens) always loaded. Layer 2 (summary, ~300 tokens) loaded on context need. Layer 3 (full SKILL.md) loaded on execution only."
+token_budget: 800
+compressed: true
+deprecated: false
 ---
 
 # Skill Index — Progressive Disclosure Engine
 
+## TL;DR
+- **Use when** searching for a CodyMaster or community skill
+- **Layered**: L1 index (always loaded) → L2 summary → L3 full
+- **Includes**: discovery, search, mastery (consolidated in v6)
+
 > **Save 90%+ tokens.** Agents scan the index first, load full skills only when executing.
 > Inspired by Loki Mode's 3-Layer Progressive Disclosure memory architecture.
 
@@ -98,6 +106,10 @@ Traditional approach: Load every SKILL.md to decide which skill to use.
 | `cm-execution` | execute, implement, plan, RARV, batch | Execute plans: batch mode, subagent-driven, parallel, or RARV |
 | `cm-continuity` | memory, context, CONTINUITY, learnings | Working memory protocol: read at start, update at end |
 | `cm-skill-mastery` | which skill, skill list, discover, help | Meta-skill: when to invoke skills, how to create new ones |
+| `cm-skill-health` | skill broken, skill drift, missing skill, stale skill, health | Audit a skill using docs drift, retro notes, validation, and gates |
+| `cm-skill-evolution` | repair skill, evolve skill, fix skill, derive skill | Recover a degraded skill with FIX, DERIVED, or CAPTURED mode |
+| `cm-skill-search` | find skill, lookup skill, which skill, search skill | Find the right skill through indexes, suggestions, and repo search |
+| `cm-skill-share` | export skill, import skill, share skill, move skill | Package and transfer skill folders safely across repos and machines |
 | `cm-safe-i18n` | translate, i18n, language, localize | Safe translation with multi-pass batching and audit gates |
 | `cm-skill-chain` | chain, pipeline, workflow, multi-step, full process | Compose skills into automated multi-step pipelines |
 | `cm-deep-search` | semantic search, find docs, large codebase, qmd | Optional power-up for semantic search across large projects |
@@ -127,8 +139,12 @@ Traditional approach: Load every SKILL.md to decide which skill to use.
 
 ### Community Skills Registry 🌐
 
-> **59 pre-indexed community skills** from skills.sh. Install on-demand: `npx skills add {source} --skill {name} -a antigravity`
-> If tech not listed here → fall back to `npx skills find "{keyword}"`
+> **STOP! Zero-Token Discovery Priority:**
+> BEFORE using this registry, check if `.cm/project-skills.md` exists in the local project.
+> It contains the pre-compiled, exact community skills needed for the project's tech stack.
+> If it doesn't exist, run `npx cm index skills` first to build it.
+> 
+> **Only use the registry below if tech is not listed** or if you need to search manually: `npx skills find "{keyword}"`
 
 #### 🖥️ Frontend Frameworks (10)
 
@@ -311,7 +327,7 @@ operations: [cm-safe-deploy, cm-identity-guard, cm-git-worktrees, cm-terminal, c
 security: [cm-secret-shield]
 product: [cm-brainstorm-idea, cm-planning, cm-ux-master, cm-ui-preview, cm-dockit, cm-project-bootstrap, cm-jtbd]
 growth: [cm-content-factory, cm-ads-tracker, cm-cro-methodology]
-orchestration: [cm-execution, cm-continuity, cm-skill-mastery, cm-skill-chain, cm-deep-search, cm-readit, cm-how-it-work]
+orchestration: [cm-execution, cm-continuity, cm-skill-mastery, cm-skill-health, cm-skill-evolution, cm-skill-search, cm-skill-share, cm-skill-chain, cm-deep-search, cm-readit, cm-how-it-work]
 commands: [cm-start, cm-dashboard, cm-status]
 # planned (no SKILL.md yet): mom-test, release-it, medical-research, tailwind-mastery, pandasai-analytics, cm-google-form
 ```

package/skills/cm-skill-mastery/SKILL.archive.md

@@ -0,0 +1,156 @@
+---
+name: cm-skill-mastery
+description: "Meta-skill for the Cody Master kit — when to invoke skills, how to create new skills, and skill discovery. Use at conversation start to establish skill discipline."
+---
+
+# Skill Mastery — Use + Create + Discover
+
+> **The meta-skill:** How to find, use, and create cm-* skills.
+
+## Part A: Using Skills
+
+### The Rule
+
+**Invoke relevant skills BEFORE any response or action.** Even 1% chance = check the skill.
+
+### Decision Flow
+
+```
+User message received
+  → Might any skill apply? (even 1%)
+    → YES: Read the skill → Follow it
+    → NO: Respond directly
+```
+
+### Skill Priority
+
+1. **Process skills first** (cm-planning, cm-debugging) — determine HOW to approach
+2. **Implementation skills second** (cm-tdd, cm-safe-deploy) — guide execution
+
+### Red Flags
+
+| Thought | Reality |
+|---------|---------|
+| "This is just a simple question" | Questions are tasks. Check for skills. |
+| "I need more context first" | Skill check BEFORE clarifying questions. |
+| "The skill is overkill" | Simple things become complex. Use it. |
+| "I remember this skill" | Skills evolve. Read current version. |
+| "Let me just do this one thing first" | Check BEFORE doing anything. |
+
+### Skill Types
+
+- **Rigid** (cm-tdd, cm-debugging): Follow exactly. Don't adapt away discipline.
+- **Flexible** (cm-planning): Adapt principles to context.
+
+---
+
+## Part B: Creating Skills
+
+### When to Create
+
+- Pattern repeated across 3+ projects
+- Complex process that needs documentation
+- Team convention that should be enforced
+
+### Skill Structure
+
+```markdown
+---
+name: cm-[skill-name]
+description: "One line: when to use this skill"
+---
+
+# [Skill Title]
+
+## Overview
+What and why. Core principle.
+
+## When to Use
+Specific triggers.
+
+## The Process
+Step-by-step instructions.
+
+## Red Flags
+What NOT to do.
+
+## Integration
+How it connects to other cm-* skills.
+```
+
+### Rules
+
+```
+✅ DO:
+- Keep under 400 lines (token optimization)
+- Use tables and code blocks for density
+- Include Red Flags section
+- Reference other cm-* skills by name
+- Test skill with real scenarios before deploying
+
+❌ DON'T:
+- Write prose when a table works
+- Duplicate content from other skills (reference instead)
+- Create skills for one-time tasks
+- Exceed 600 lines without good reason
+```
+
+### Token Optimization
+
+| Technique | Saves |
+|-----------|-------|
+| Tables over prose | ~40% |
+| Code blocks over explanation | ~30% |
+| Reference other skills vs duplicate | ~50% |
+| Remove obvious examples | ~20% |
+
+---
+
+## Part C: Discovering Skills
+
+### Adaptive Skills Discovery
+
+When you encounter something you don't have a skill for:
+
+```
+1. DETECT  → "I need to do X but no matching skill"
+2. SEARCH  → npx skills find "{keyword}"
+3. REVIEW  → Read the SKILL.md — safe? relevant?
+4. ASK     → "Found skill '{name}'. Install?"
+5. INSTALL → npx skills add {source} --skill {name} -a antigravity
+6. USE     → Apply the skill
+7. LOG     → Record in .cm-skills-log.json
+```
+
+### Safety Rules
+
+- Always show user what you found before installing
+- Prefer known repos (vercel-labs/agent-skills)
+- Project-level by default, global only if agreed
+- Check `npx skills list` to avoid duplicates
+- Never override existing cm-* skills with external ones
+
+---
+
+## The Cody Master Kit (14 skills)
+
+| # | Skill | Purpose |
+|---|-------|---------|
+| 1 | `cm-project-bootstrap` | Start new projects |
+| 2 | `cm-brainstorm-idea` | Strategic analysis gate for enhancements (9 Windows + Double Diamond) |
+| 3 | `cm-planning` | Brainstorm + write plans |
+| 4 | `cm-execution` | Execute plans (batch/subagent/parallel) |
+| 5 | `cm-tdd` | Test-driven development |
+| 6 | `cm-quality-gate` | Test + verify + frontend safety |
+| 7 | `cm-code-review` | Request + receive + finish branch |
+| 8 | `cm-safe-deploy` | 6-gate deploy pipeline |
+| 9 | `cm-safe-i18n` | i18n batching + safety |
+| 10 | `cm-debugging` | Systematic root-cause debugging |
+| 11 | `cm-terminal` | Terminal command monitoring |
+| 12 | `cm-git-worktrees` | Isolated workspaces |
+| 13 | `cm-skill-mastery` | This skill (meta) |
+| 14 | `cm-identity-guard` | Git/deploy identity safety |
+
+## The Bottom Line
+
+**Skills are discipline, not overhead. Use them. Create them. Never skip them.**

package/skills/cm-skill-mastery/SKILL.md

@@ -1,156 +1,26 @@
 ---
 name: cm-skill-mastery
-description: "Meta-skill for the Cody Master kit — when to invoke skills, how to create new skills, and skill discovery. Use at conversation start to establish skill discipline."
+description: "[Deprecated] discovery and meta-skill merged. Use `cm-skill-index` instead."
+deprecated: true
+merged_into: cm-skill-index
 ---
 
-# Skill Mastery — Use + Create + Discover
+# cm-skill-mastery — Deprecated
 
-> **The meta-skill:** How to find, use, and create cm-* skills.
+> ⚠️ This skill is deprecated as of CodyMaster v6.0.0 and will be removed in v6.1.0.
+>
+> **Use `cm-skill-index` instead.** discovery and meta-skill merged.
+>
+> See [docs/migration-v2.md](../../docs/migration-v2.md) for the full mapping.
 
-## Part A: Using Skills
+The original content is preserved at [SKILL.archive.md](SKILL.archive.md) for reference.
 
-### The Rule
+## Migration
 
-**Invoke relevant skills BEFORE any response or action.** Even 1% chance = check the skill.
-
-### Decision Flow
-
-```
-User message received
-  → Might any skill apply? (even 1%)
-    → YES: Read the skill → Follow it
-    → NO: Respond directly
+```bash
+# Old:           cm <use this skill>
+# New (v6.0+):   cm skill-index <equivalent action>
 ```
 
-### Skill Priority
-
-1. **Process skills first** (cm-planning, cm-debugging) — determine HOW to approach
-2. **Implementation skills second** (cm-tdd, cm-safe-deploy) — guide execution
-
-### Red Flags
-
-| Thought | Reality |
-|---------|---------|
-| "This is just a simple question" | Questions are tasks. Check for skills. |
-| "I need more context first" | Skill check BEFORE clarifying questions. |
-| "The skill is overkill" | Simple things become complex. Use it. |
-| "I remember this skill" | Skills evolve. Read current version. |
-| "Let me just do this one thing first" | Check BEFORE doing anything. |
-
-### Skill Types
-
-- **Rigid** (cm-tdd, cm-debugging): Follow exactly. Don't adapt away discipline.
-- **Flexible** (cm-planning): Adapt principles to context.
-
----
-
-## Part B: Creating Skills
-
-### When to Create
-
-- Pattern repeated across 3+ projects
-- Complex process that needs documentation
-- Team convention that should be enforced
-
-### Skill Structure
-
-```markdown
----
-name: cm-[skill-name]
-description: "One line: when to use this skill"
----
-
-# [Skill Title]
-
-## Overview
-What and why. Core principle.
-
-## When to Use
-Specific triggers.
-
-## The Process
-Step-by-step instructions.
-
-## Red Flags
-What NOT to do.
-
-## Integration
-How it connects to other cm-* skills.
-```
-
-### Rules
-
-```
-✅ DO:
-- Keep under 400 lines (token optimization)
-- Use tables and code blocks for density
-- Include Red Flags section
-- Reference other cm-* skills by name
-- Test skill with real scenarios before deploying
-
-❌ DON'T:
-- Write prose when a table works
-- Duplicate content from other skills (reference instead)
-- Create skills for one-time tasks
-- Exceed 600 lines without good reason
-```
-
-### Token Optimization
-
-| Technique | Saves |
-|-----------|-------|
-| Tables over prose | ~40% |
-| Code blocks over explanation | ~30% |
-| Reference other skills vs duplicate | ~50% |
-| Remove obvious examples | ~20% |
-
----
-
-## Part C: Discovering Skills
-
-### Adaptive Skills Discovery
-
-When you encounter something you don't have a skill for:
-
-```
-1. DETECT  → "I need to do X but no matching skill"
-2. SEARCH  → npx skills find "{keyword}"
-3. REVIEW  → Read the SKILL.md — safe? relevant?
-4. ASK     → "Found skill '{name}'. Install?"
-5. INSTALL → npx skills add {source} --skill {name} -a antigravity
-6. USE     → Apply the skill
-7. LOG     → Record in .cm-skills-log.json
-```
-
-### Safety Rules
-
-- Always show user what you found before installing
-- Prefer known repos (vercel-labs/agent-skills)
-- Project-level by default, global only if agreed
-- Check `npx skills list` to avoid duplicates
-- Never override existing cm-* skills with external ones
-
----
-
-## The Cody Master Kit (14 skills)
-
-| # | Skill | Purpose |
-|---|-------|---------|
-| 1 | `cm-project-bootstrap` | Start new projects |
-| 2 | `cm-brainstorm-idea` | Strategic analysis gate for enhancements (9 Windows + Double Diamond) |
-| 3 | `cm-planning` | Brainstorm + write plans |
-| 4 | `cm-execution` | Execute plans (batch/subagent/parallel) |
-| 5 | `cm-tdd` | Test-driven development |
-| 6 | `cm-quality-gate` | Test + verify + frontend safety |
-| 7 | `cm-code-review` | Request + receive + finish branch |
-| 8 | `cm-safe-deploy` | 6-gate deploy pipeline |
-| 9 | `cm-safe-i18n` | i18n batching + safety |
-| 10 | `cm-debugging` | Systematic root-cause debugging |
-| 11 | `cm-terminal` | Terminal command monitoring |
-| 12 | `cm-git-worktrees` | Isolated workspaces |
-| 13 | `cm-skill-mastery` | This skill (meta) |
-| 14 | `cm-identity-guard` | Git/deploy identity safety |
-
-## The Bottom Line
-
-**Skills are discipline, not overhead. Use them. Create them. Never skip them.**
+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-skill-search/SKILL.archive.md

@@ -0,0 +1,49 @@
+---
+name: cm-skill-search
+description: "Find the best CodyMaster skill using the shipped indexes, profiles, docs, and contextual suggestions."
+---
+
+# cm-skill-search
+
+Use this skill when you need to find the right CodyMaster skill quickly and avoid loading the wrong `SKILL.md`.
+
+## Search order
+
+1. Fast path
+   - `cm suggest --project .`
+2. Library index
+   - `docs/skills/index.md`
+   - `docs/skills/*.md` category pages
+3. Progressive disclosure
+   - `skills/cm-skill-index/SKILL.md`
+4. Raw filesystem search
+   - `rg -n "<keyword>" skills docs README.md`
+5. Fallback
+   - if nothing matches, use `cm-skill-health` to check whether the missing skill is docs drift or a real gap
+
+## Query workflow
+
+1. Normalize the intent into 2-5 keywords.
+2. Search category pages before opening full skills.
+3. Open only the top 1-3 candidate `SKILL.md` files.
+4. Prefer the skill whose triggers, outputs, and lifecycle placement best match the task.
+5. If two skills overlap:
+   - choose the earlier lifecycle gate first
+   - example: `cm-brainstorm-idea` before `cm-planning`
+
+## Tie-breakers
+
+- Need diagnosis before repair: choose `cm-skill-health`
+- Need to repair a skill: choose `cm-skill-evolution`
+- Need to distribute a skill pack: choose `cm-skill-share`
+- Need the general index first: choose `cm-skill-index`
+
+## Output
+
+```md
+## Skill Search Result
+- Task: ...
+- Best match: cm-...
+- Runner-up: cm-...
+- Why: ...
+```

package/skills/cm-skill-search/SKILL.md

@@ -0,0 +1,26 @@
+---
+name: cm-skill-search
+description: "[Deprecated] discovery merged. Use `cm-skill-index` instead."
+deprecated: true
+merged_into: cm-skill-index
+---
+
+# cm-skill-search — Deprecated
+
+> ⚠️ This skill is deprecated as of CodyMaster v6.0.0 and will be removed in v6.1.0.
+>
+> **Use `cm-skill-index` instead.** discovery merged.
+>
+> See [docs/migration-v2.md](../../docs/migration-v2.md) for the full mapping.
+
+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 skill-index <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-skill-share/SKILL.archive.md

@@ -0,0 +1,58 @@
+---
+name: cm-skill-share
+description: "Package, review, export, and import CodyMaster skill folders safely across machines or teams."
+---
+
+# cm-skill-share
+
+Use this skill when moving a CodyMaster skill between repos, machines, or teammates.
+
+## What to share
+
+Always treat a skill as a folder, not just `SKILL.md`.
+
+Check for:
+- `SKILL.md`
+- templates
+- scripts
+- references
+- assets
+- profile/index entries that must move with it
+
+## Export checklist
+
+1. Validate the source skill.
+   - `npm run validate:skills`
+2. Inspect companion files inside the skill folder.
+3. Note external dependencies the target repo must already have.
+4. Copy the entire folder.
+5. Update destination discovery surfaces if the skill becomes user-facing.
+
+## Import checklist
+
+1. Place the folder under `skills/cm-.../`
+2. Run:
+   - `npm run validate:skills`
+   - `npm run check:skills`
+3. Add it to:
+   - `skills/profiles/full.txt`
+   - docs skill index pages
+   - README only if the skill is part of the public catalog
+4. Verify referenced commands and files exist in the target repo.
+
+## Red flags
+
+- Do not import only the markdown file if the skill depends on scripts or templates.
+- Do not advertise the skill publicly before it is indexed and validated.
+- Do not overwrite an existing skill without comparing behavior and references first.
+
+## Output
+
+```md
+## Skill Share
+- Skill: cm-...
+- Direction: export | import
+- Companion files checked: yes | no
+- Discovery surfaces updated: yes | no
+- Validation: pass | fail
+```

package/skills/cm-skill-share/SKILL.md

@@ -0,0 +1,26 @@
+---
+name: cm-skill-share
+description: "[Deprecated] skill lifecycle merged. Use `cm-skill-evolution` instead."
+deprecated: true
+merged_into: cm-skill-evolution
+---
+
+# cm-skill-share — Deprecated
+
+> ⚠️ This skill is deprecated as of CodyMaster v6.0.0 and will be removed in v6.1.0.
+>
+> **Use `cm-skill-evolution` instead.** skill lifecycle merged.
+>
+> See [docs/migration-v2.md](../../docs/migration-v2.md) for the full mapping.
+
+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 skill-evolution <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-sprint-bus/SKILL.md

@@ -1,5 +1,18 @@
+---
+name: cm-sprint-bus
+description: "Use to run the full sprint pipeline: brainstorm → plan → design → tdd → build → review → qa → security → ship → monitor → retro."
+token_budget: 1500
+compressed: true
+deprecated: false
+---
 # cm-sprint-bus — opinionated pipeline + artifacts
 
+## TL;DR
+- **Use to** drive the full sprint: brainstorm → ship → retro
+- **Phases**: brainstorm, plan, design, tdd, build, review, qa, security, ship, monitor, retro
+- **Each phase**: writes Markdown artifact + handoff JSON
+- **CLI**: cm sprint init|status|complete|skip|dry-run
+
 ## Pipeline
 
 `brainstorm → plan → design → tdd → build → review → qa → security → ship → monitor → retro`