Scan a Cargo workspace or package monorepo and refresh per-member `CLAUDE.md` files plus a thin root `CLAUDE.md`. User-only maintenance workflow for keeping workspace-local AI context accurate after refactors, member additions, export changes, or major architectural shifts.
$request: Optional scope or refresh note such as all crates, only packages/api-*, or refresh workspace docs after adding the sql crate.Refresh the root and per-member CLAUDE.md files so each workspace member has accurate, self-contained local guidance and the root stays thin and project-wide.
Determine:
CLAUDE.md filesLoad references/workspace-discovery.md for:
Stop early if:
Success criteria: The workspace shape and refresh scope are explicit before discovery starts.
For every in-scope member, inventory:
Rules:
pub or raw export counts with the real public surfaceLoad references/workspace-discovery.md and complete the relevant discovery steps for the detected monorepo shape.
Success criteria: You have enough concrete inventory to write self-contained member docs without placeholders or false surface claims.
CLAUDE.md filesFor each in-scope member, update or create a focused local CLAUDE.md that covers:
Load:
references/output-contract.md for required sections, size targets, and verification rulesreferences/package-template.md for library or package membersreferences/app-template.md for apps, binaries, or entrypoint-heavy membersWriting rules:
Success criteria: Every targeted member has an accurate, self-contained CLAUDE.md.
CLAUDE.mdTreat the root file as the project-wide router:
Rules:
Load references/output-contract.md for the root-file expectations and budget rules.
Success criteria: Root stays thin and project-wide while member detail lives where Claude will lazy-load it.
Validate the refresh before declaring completion:
CLAUDE.mdLoad references/output-contract.md for verification gates and budget targets.
If verification fails:
Success criteria: The workspace memory is compact, member-local, and actually useful to future agents.
Summarize:
Do not claim a perfect refresh if the workspace is only partially covered or if the requested scope excluded some members.
Success criteria: The user gets a clear summary of what workspace memory was refreshed and how complete it is.
context: fork; this workflow writes into the active repository.paths:; this is a generic maintenance skill.SKILL.md.CLAUDE.md; push member detail down.references/workspace-discovery.md
Use for workspace detection order, member discovery rules, and exported-surface versus raw-visibility guidance.
references/output-contract.md
Use for required member/root sections, budget rules, and verification gates.
references/package-template.md
Use when refreshing library-style members.
references/app-template.md
Use when refreshing binaries, apps, servers, or entrypoint-heavy members.
Report: