archive-analysis

It works by discovering untracked or temporary markdown files, classifying them for archiving, extracting actionable insights into a central task tracker like TODO.md, and moving items into an archive directory with date-based naming to keep workspaces uncluttered.

The best way to clean up temporary analysis notes is to archive them, which classifies old markdown files, extracts insights to a central task tracker, and moves items into an archive folder to reduce search noise in the repository.

Yes, you need Python 3.10+ and Typer for the CLI to organize untracked markdown files. The Skill reads the repository structure to ensure safe archiving with guardrails.

Yes, you can extract insights to TODO.md before moving files. The Skill discovers untracked markdown notes, extracts actionable insights into a central task-tracking file, and then moves the items into an archive directory.

Yes, archiving analysis files preserves git history for traceability. The Skill moves files into an archive folder with semantic, date-based naming while maintaining full git history across the repository.

A limitation is that auto-discovering untracked markdown files requires strict repository structure reading to ensure safe archiving with guardrails, meaning unexpected directory changes could impact the classification and extraction process.