cleanup-project

Automate project cleanup by running a skill that analyzes your active languages and frameworks to prune unused guides, archive stale tasks, and consolidate memory files within the .claude directory. It systematically identifies outdated artifacts and updates documentation to reflect the cleaned state.

Archive stale tasks and consolidate memory files by leveraging automated stack analysis to detect active frameworks, then systematically archiving or removing outdated project artifacts. This approach consolidates memory into quarterly summaries, reducing your project footprint and improving structural clarity.

Stack analysis identifies active languages and frameworks within your project to determine which skill guides are no longer relevant. It then prunes unused guides through archiving or deletion, ensuring only documentation matching your current active stack remains in the directory.

You can reduce your project footprint safely by archiving rather than deleting unused guides and stale tasks. The cleanup process systematically identifies outdated artifacts within the .claude directory and updates manifests to ensure active workflows remain unaffected.

Run automated project cleanup after a major project refactor where languages or frameworks were removed, or when stale tasks accumulate and memory files become fragmented. This streamlines code organization by pruning irrelevant artifacts and consolidating memory into manageable summaries.

The cleanup-project skill requires no external dependencies to analyze and optimize your .claude directory. It operates independently using internal scripts and references to detect active stacks, prune unused guides, archive stale tasks, and update manifests.