codymaster 4.8.0 → 5.2.0

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

@@ -0,0 +1,83 @@
+---
+name: cm-skill-evolution
+description: "Repair or extend CodyMaster skills with a three-mode loop: FIX, DERIVED, and CAPTURED, grounded in current repo tooling."
+---
+
+# cm-skill-evolution
+
+Use this skill after `cm-skill-health` identifies a degraded or broken skill, or when `cm advisory handoff --for cm-skill-evolution` produces a structured recovery note.
+
+## Modes
+
+### FIX
+Use when the skill should exist already but is inaccurate, broken, or partially missing.
+
+Checklist:
+- repair broken references
+- restore missing support files
+- align docs and profiles
+- re-run skill validation and test gate
+
+### DERIVED
+Use when the original promise was too ambitious, but the repo has enough primitives to ship a truthful MVP.
+
+Checklist:
+- keep the same user problem
+- reduce claims to what the code can support today
+- reuse existing repo building blocks instead of inventing a new subsystem
+
+### CAPTURED
+Use when the main value is operational learning rather than a new code path.
+
+Checklist:
+- append the lesson with `cm retro --project . --tool skill --note "..."`
+- record durable context in `.cm/CONTINUITY.md`
+- update the relevant skill so future sessions do not repeat the same failure
+
+## Evolution Loop
+
+1. Start from the health note.
+   - Preferred source: `cm advisory handoff --for cm-skill-evolution`
+2. Pick one mode only.
+3. Define the smallest truthful recovery.
+4. Patch the skill and its discovery surfaces.
+5. Verify:
+   - `npm run validate:skills`
+   - `npm run check:skills`
+   - repo test gate if code or docs wiring changed materially
+6. Capture the lesson in retro and continuity.
+
+## Decision guide
+
+- The feature existed and drifted: `FIX`
+- The changelog promised more than the repo ever shipped: `DERIVED`
+- The issue is mainly process and should inform future work: `CAPTURED`
+
+## Output
+
+```md
+## Skill Evolution
+- Skill: cm-...
+- Mode: FIX | DERIVED | CAPTURED
+- Change: ...
+- Verification: ...
+- Learning captured: yes | no
+```
+
+Preferred advisory input:
+
+```md
+## Advisory Handoff
+- Consumer: cm-skill-evolution
+- 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: ...
+```

package/skills/cm-skill-health/SKILL.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-index/SKILL.md

@@ -98,6 +98,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 +131,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 +319,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-search/SKILL.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-share/SKILL.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-sprint-bus/SKILL.md

@@ -1,3 +1,7 @@
+---
+name: cm-sprint-bus
+description: "Use to run the full sprint pipeline: brainstorm → plan → design → tdd → build → review → qa → security → ship → monitor → retro."
+---
 # cm-sprint-bus — opinionated pipeline + artifacts
 
 ## Pipeline

package/skills/cm-start/SKILL.md

@@ -13,16 +13,12 @@ When this workflow is called, the AI Assistant should execute the following acti
     Per `_shared/helpers.md#Load-Working-Memory` — **use Smart Spine order:**
     1. Check `.cm/context-bus.json` → any active pipeline? any prior skill output to reuse?
     2. Load L0 indexes: `learnings-index.md` (~100 tok) + `skeleton-index.md` (~500 tok)
-       > **If OpenViking backend active:** Skip step 2 — engine auto-serves L0/L1 via `cm_resolve`.
     3. Scope-filter learnings via `cm_query` — only load what matches current objective
-       > **If OpenViking:** `cm_query` uses vector semantic search — broader recall, fewer missed learnings.
     4. Read `CONTINUITY.md` → set Active Goal to the new objective
     5. Run token budget check: `cm continuity budget` → confirm no category is over soft limit
 
     > ⚡ Total context load: ~700 tokens. Full load used to be ~3,200.
     > Only escalate to L2 (full files) if L0 index explicitly flags a match.
-    > With OpenViking: L0 is auto-maintained — no stale index risk.
-
 0.5. **Skill Coverage Check (Adaptive Discovery):**
     - Scan the objective for technologies, frameworks, or patterns mentioned
     - Cross-reference with `cm-skill-index` Layer 1 triggers
@@ -85,11 +81,5 @@ When this workflow is called, the AI Assistant should execute the following acti
     - Record any new learnings or decisions made during this workflow
     - If inside a skill chain: `cm continuity bus` → verify context bus reflects completed step
     - Refresh L0 indexes: `cm continuity index` (auto-runs on `addLearning`, manual refresh here)
-      > **If OpenViking:** Skip manual index refresh — engine maintains L0/L1 automatically.
-
 > **Note for AI:** If this is a brand new project, suggest running `cm-project-bootstrap` first.
 > If the working environment has a risk of accidentally switching accounts/projects, remind about `cm-identity-guard` (Per `_shared/helpers.md#Identity-Check`).
->
-> **OpenViking tip:** If the project uses many learnings/decisions (>100 entries) or needs semantic
-> search beyond keyword matching, suggest switching to the Viking backend:
-> `storage.backend: viking` in `.cm/config.yaml` + `pip install openviking && openviking start`

package/skills/cm-tdd/SKILL.md

@@ -1,7 +1,7 @@
 ---
-
-## name: cm-tdd
+name: cm-tdd
 description: Use when implementing any feature or bugfix, before writing implementation code
+---
 
 # Test-Driven Development (TDD)
 

package/skills/profiles/full.txt

@@ -46,8 +46,12 @@ cm-second-opinion-cli
 cm-secret-shield
 cm-security-gate
 cm-skill-chain
+cm-skill-evolution
+cm-skill-health
 cm-skill-index
 cm-skill-mastery
+cm-skill-search
+cm-skill-share
 cm-sprint-bus
 cm-start
 cm-status