cleanup

Archive completed Belmont features and audit convention files interactively.

4|2|Updated Jan 29, 2026

Search Tags:#tooling #cleanup #conventions #milestones #notes #archiving #belmont

Ready to run

npx skills add https://github.com/blake-simpson/belmont --skill cleanup-blake-simpson

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

Interactive, per-item cleanup: prompts user to archive, keep, or delete each completed feature and milestone.
Non-destructive by default: prioritizes keeping data unless explicitly approved for archive or removal.
Audits convention files and notes to ensure alignment with current project scope and tooling, with optional automated summaries.

Quick Start

Initiate cleanup to archive completed features, purge stale milestone files, trim NOTES.md, and audit conventions while preserving active work.

Frequently Asked Questions about cleanup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I reduce Belmont state token bloat from completed features and milestones?▼

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.

What is the best way to trim NOTES.md and audit convention files in an ongoing project?▼

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.

Does Belmont cleanup support interactive prompts to safely archive or delete project state?▼

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.

Can I audit tool convention files without permanently deleting archived milestones?▼

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.

Why does my agent slow down when the .belmont state directory accumulates outdated conventions?▼

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.

When should I avoid using automated state cleanup on my project milestones?▼

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.