propagate-templates
Skill4 starsChanged 4 months agoMITView on GitHub
Propagate the two remaining duplicated artifacts — principled-docs scaffolding templates and the cross-plugin check-gh-cli.sh — then verify zero drift. Use after editing either canonical source.
In this repository5 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- check-ciSkill
- lintSkill
- test-hooksSkill
The file
Files
Propagate Templates — Canonical Copy Sync
Most shared code no longer needs propagating. ADR-018 moved same-plugin shared scripts
into each plugin's lib/, referenced as ${CLAUDE_PLUGIN_ROOT}/lib/<name> — one copy,
so there is nothing to sync and nothing that can drift.
Two cases genuinely still need copies, and this skill covers exactly those.
Command
/propagate-templatesWorkflow
1. principled-docs scaffolding templates
Each generative skill ships the template it writes, so the scaffold templates are duplicated on purpose. Copy each canonical template to its consuming skill:
plugins/principled-docs/skills/scaffold/templates/core/proposal.md→plugins/principled-docs/skills/new-proposal/templates/proposal.mdplugins/principled-docs/skills/scaffold/templates/core/plan.md→plugins/principled-docs/skills/new-plan/templates/plan.mdplugins/principled-docs/skills/scaffold/templates/core/decision.md→plugins/principled-docs/skills/new-adr/templates/decision.mdplugins/principled-docs/skills/scaffold/templates/core/architecture.md→plugins/principled-docs/skills/new-architecture-doc/templates/architecture.md
2. Cross-plugin check-gh-cli.sh
principled-github, principled-quality and principled-release install independently, and
${CLAUDE_PLUGIN_ROOT} resolves to a single plugin, so a script all three need has to
exist three times. Canonical lives in principled-github:
plugins/principled-github/lib/check-gh-cli.sh→plugins/principled-quality/lib/check-gh-cli.shplugins/principled-github/lib/check-gh-cli.sh→plugins/principled-release/lib/check-gh-cli.sh
3. Verify
bash plugins/principled-docs/skills/scaffold/scripts/check-template-drift.sh
bash scripts/check-cross-plugin-drift.shBoth must report PASS.
Then confirm nothing references a path that no longer exists:
bash scripts/check-skill-references.shWhat this skill does NOT cover
lib/ contents in any plugin — task-manifest.sh, parse-plan.sh, run-checks.sh,
task-db.sh, next-number.sh, validate-structure.sh, check-gh-cli.sh within
principled-github. These have one copy each. Edit them in place; there is nothing to
propagate. If you find yourself copying one of these into a skill directory, that is a
regression against ADR-018.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

