What problem does it solve?
Editing SKILL.md files across the repository's parallel skill trees (.claude/skills, .opencode/skills, .agents/skills) without following the repo's mirror contracts silently desynchronizes cross-platform skill surfaces, breaks CI drift checks, and orphans dependent shims, leading to broken user experiences and failed releases.
Core Features & Use Cases
- Skill Classification Guidance: Walks through categorizing skills into mirrored, adapter, divergent, opencode-only, and additional contract types per the repo's skill-mirrors.ts configuration.
- Edit Rule Enforcement: Mandates dual-tree byte-identical edits for mirrored skills, shim maintenance for adapter and no-entry skills, and correct inclusion in shipping paths for npm-published skills.
- Validation Workflow: Includes required pre-publish checks like running drift checks, verifying byte identity for mirrored pairs, and creating release fragments for changes that touch core config files.
- Use Case: For example, if you need to update the trigger description of a mirrored architect skill, this skill ensures you edit both the .opencode and .claude copies identically, then validate no drift warnings are introduced.
Quick Start
Use the editing-skills skill to update the description of the brainstorm skill in both its mirrored .opencode and .claude locations, then run drift:check to confirm no desync warnings appear.
