update-claudemd — Claude Code skill: what it does, how to install
update-claudemd — a skill that checks CLAUDE.md and the topic files in .claude/rules/ against the actual code and commit history, then trims what went stale and regroups the instructions.
no license ★ 276 updated 2026-10-29
/plugin marketplace add gupsammy/Claudest
/plugin install claude-coding@ClaudestWhat update-claudemd does
The skill re-checks a project's CLAUDE.md and everything under .claude/rules/*.md against what the repository holds now, plus commits made after each file was last touched. Structure follows progressive disclosure: the root file keeps project identity, invariants shared by most tasks, and pointers; narrow notes move into topic files.
Before reading any code it sizes the job. How many commits landed since the last CLAUDE.md edit, and how many files git tracks, decide how many shards the scan gets, capped at 4. Then 3 + N Explore agents start at once. One classifies every section and looks for dead paths, wrong commands and duplicated text. Another replays git log for each instruction file separately. Limits are advisory: roughly 120 lines for CLAUDE.md with 150 as the ceiling, about 300 per topic file, and an overage gets flagged rather than blocked.
Every topic file it writes has to carry paths: in the frontmatter, because files in .claude/rules/ otherwise load at SessionStart in every session. No CLAUDE.md at the repo root means the skill stops instead of generating one. A git repository is required too, since each staleness window starts at that file's own commit date. The user-level ~/.claude/CLAUDE.md is left alone.
What it helps with
- sync
CLAUDE.mdwith code that moved since the last edit - strip dead paths and stale commands from project instructions
- split an oversized
CLAUDE.mdinto files under.claude/rules/ - spot duplicated guidance between the root file and its topics
- catch topic files that nothing links to from the index
Example prompts for the agent
- Update CLAUDE.md, it drifted away from the codebase.
- Reorganize CLAUDE.md and move subsystem notes into topic files.
- Audit .claude/rules/ and sync those files with the code.
How to install update-claudemd
1Plugin marketplace
/plugin marketplace add gupsammy/Claudest/plugin install claude-coding@ClaudestThis installs the whole claude-coding plugin with all its skills
2Skills CLI (Vercel)
npx skills add gupsammy/Claudest --skill update-claudemd -a claude-code3Manually: put the files in place
~/.claude/skills/update-claudemd/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/update-claudemd/
1Skills CLI (Vercel)
npx skills add gupsammy/Claudest --skill update-claudemd -a codex2Manually: put the files in place
.agents/skills/update-claudemd/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add gupsammy/Claudest --skill update-claudemd -a cursor2Manually: put the files in place
.cursor/skills/update-claudemd/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install gupsammy/Claudest plugins/claude-coding/skills/update-claudemd2Manually: put the files in place
.github/skills/update-claudemd/SKILL.md1Skills CLI (Vercel)
npx skills add gupsammy/Claudest --skill update-claudemd -a gemini-cli2Platform CLI
gemini skills install https://github.com/gupsammy/Claudest --path plugins/claude-coding/skills/update-claudemdManually: put the files in place
.devin/skills/update-claudemd/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about update-claudemd
How do I install update-claudemd in Claude Code?
From the marketplace: run /plugin marketplace add gupsammy/Claudest, then /plugin install claude-coding@Claudest.
What does update-claudemd do?
It compares CLAUDE.md and the files in .claude/rules/ with the code and git history, removes what went stale, and sorts the instructions into topic files carrying paths: frontmatter.
What does the skill need to run?
A git repository with commit history and an existing CLAUDE.md at the project root. Without that root file the skill stops and will not create one.