agentleFS
Sign inStart free
p10ns11yp10ns11y/skills/skill-rename-propagation/SKILL.md

skill-rename-propagation

Skill2 starsChanged 42 days agoMITView on GitHub

One-pass rename of a skill: folder, frontmatter name, Cursor rules, validators, README catalog, pack scripts, workflows, and consuming-repo references. Use when renaming skills (e.g. looper → control-graph) or after folder moves. Triggers: skill rename, rename propagation, rename skill, looper rename.

The file

Create a free account to mount
Files
SKILL.md

skill-rename-propagation

Load rule: Formal checklist is SoT. Aligns with QUALITY.md rename policy.

// Inputs
OLD, NEW  // kebab-case skill names
LIB       // skills library root
PROJECTS  // optional consuming checkouts

// Axioms
A1  One pass: grep → rewrite → validate → commit  (no half-rename)
A2  Keep discovery alias in description for ≥1 release if OLD was public
A3  Update validators that hardcode name === OLD
A4  Symlinks ~/.cursor/skills/OLD and rules/OLD.mdc must be repointed
A5  Archive may keep OLD paths as history — do not "fix" archive unless intentional
A6  Evaluate(δ) ≔ (C, E, η)

Related: dual-copy-skill-publish · author-workflow-skill · master-planner.

Use / skip

UseSkip
renaming skill folder/public namecosmetic title-only in body
after git mv left broken linkspure content edit without name change
pack/README still point at OLD

One-pass checklist

[ ] 1. git mv LIB/OLD LIB/NEW  (+ rules/OLD.mdc → rules/NEW.mdc if any)
[ ] 2. Frontmatter name: NEW
[ ] 3. Body titles, links, script paths
[ ] 4. Optional redirect OLD/SKILL.md → NEW (legacy discovery) + description alias
[ ] 5. README catalog + QUALITY + pack scripts (master-planner pull-skills.sh)
[ ] 6. Workflows .md/.rhai skill_chain strings
[ ] 7. Consuming projects: AGENTS.md, .agents/skills symlinks
[ ] 8. Run skill validator if present
[ ] 9. rg OLD across LIB — residual only intentional aliases / archive / redirect
[ ] 10. Commit with clear rename message (push=HITL)

Commands

OLD=looper NEW=control-graph
LIB="${SKILLS_ROOT:-$HOME/Work/personal/skills}"
cd "$LIB"

rg -n --glob '!**/.git/**' --glob '!archive/**' "\\b${OLD}\\b" || true

# after git mv + content rewrites
node "$NEW/scripts/validate-skill.mjs" 2>/dev/null || true
rg -n --glob '!**/.git/**' --glob '!archive/**' --glob "!**/${OLD}/**" "\\b${OLD}\\b" || true

Consuming repo

ln -sfn "$LIB/$NEW" .agents/skills/$NEW
rm -f .agents/skills/$OLD
# fix AGENTS.md table rows

Done when

  • name: frontmatter is NEW
  • No accidental OLD paths in active (non-archive, non-alias, non-redirect) files
  • Validator passes if present
  • User symlinks / pack scripts documented or updated
  • Commit created

Anti-patterns

¬Do
rename folder onlybreak frontmatter + rules + packs
leave pack scripts on OLDagents pull missing skill
delete OLD triggers immediatelykeep alias in description/redirect ≥1 release
mass-edit archive distill historyleave archive; note supersession

Done_when cmds: rg -n '^name:' "$NEW/SKILL.md" · rg -n "\\b$OLD\\b" --glob '!archive/**' --glob "!$OLD/**" · validator exit 0.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free