Archive completed Belmont features and audit convention files interactively.
npx skills add https://github.com/blake-simpson/belmont --skill cleanup-blake-simpson
Please help me install this Agent Skill. Skill: cleanup Source: https://github.com/blake-simpson/belmont/tree/main/plugin/skills/cleanup Command: npx skills add https://github.com/blake-simpson/belmont --skill cleanup-blake-simpson
Belmont projects accumulate completed features, archived milestones, long NOTES.md files, and outdated CLAUDE.md/AGENTS.md conventions, inflating the context window and slowing agents. This Skill provides a safe, interactive way to prune state while preserving active context.
Initiate cleanup to archive completed features, purge stale milestone files, trim NOTES.md, and audit conventions while preserving active work.
High-intent search queries and answers about installing and using this skill.
To reduce Belmont state token bloat, you can interactively archive completed features and purge stale milestone files. This process safely prunes the .belmont state directory while preserving your active project context.
Trimming NOTES.md and auditing convention files involves reviewing long notes and outdated CLAUDE.md/AGENTS.md configurations against current project scope. This ensures alignment and generates optional summaries to maintain a lean agent context.
Yes, Belmont cleanup uses interactive, per-item prompts to safely archive, keep, or delete completed features and milestones. It is non-destructive by default, prioritizing data retention unless explicit approval is given for removal.
Yes, you can audit tool convention files while keeping archived milestones intact. The cleanup mechanism applies guardrails to ensure safe archiving and trimming without destructive actions, unless you explicitly approve item removal.
Agents slow down because accumulated outdated conventions, long NOTES.md files, and completed features inflate the context window. Auditing and pruning these files reduces token bloat and restores agent processing speed.
You should avoid automated state cleanup if your project lacks interactive guardrails or if you need to retain all historical milestone data. The tool prioritizes keeping data unless you explicitly approve destructive archiving or removal actions.
blake-simpsonSummarize Belmont project state into a formatted status report from PRD.md and PROGRESS.md.
scooter-lacroixIsolate AI agent outputs to cache files to prevent context window pollution.
z1439527767Create concise AGENTS.md or CLAUDE.md files from repository tooling and conventions.
BurburtonTrim project context to essential task_goal, constraints, and artifacts.
