cleanup-project

Automate project cleanup by analyzing your active stack to prune unused skills and stale tasks. The tool scans project files and dependency manifests to identify active languages and frameworks, selectively archiving or deleting irrelevant guides within the `.claude/` directory.

The best way to remove outdated framework guides after a migration is to run an automated stack analysis. It detects your active languages and frameworks to determine which guides are still relevant, automatically removing irrelevant dependencies to free up space and simplify your AI's context.

Stack analysis for consolidating memory files works by scanning project files and dependency manifests to determine relevance. It identifies active languages and frameworks, selectively archives or deletes irrelevant skills, and updates your project documentation to reflect the current stack.

Yes, it can clean up the `.claude/` directory safely by analyzing the active stack before pruning. It requires analysis of project files and dependency manifests to determine relevance, ensuring only unused language guides and stale tasks are archived or deleted while active workflows remain untouched.

You should run a project cleanup task to archive stale tasks whenever your project experiences significant changes, such as a technology migration. Pruning unused guides and consolidating memory files reduces project bloat and improves AI efficiency.