session-tidy

Run the session-tidy audit to scan all files under sessions/ for naming violations, incomplete frontmatter, stale statuses, and orphaned next-steps. It presents a structured report of proposed changes and executes them only after you approve.

Session files must match the pattern '[N]. [Title].md' or '[N]. [Title].html', where N is the session number and Title is a 2-5 word outcome summary. Files like 'Session 1.md' or names with parenthetical suffixes are flagged for renaming.

Yes, it supports three backends with first-success-wins detection: a headless Obsidian CLI, the Obsidian MCP tools, or a local vault directory at ~/.claude/vault/. Local and headless backends use Bash commands like mv and Grep instead of MCP tools.

The audit scans session content for sections containing 'Next', 'Queued', 'TODO', or similar markers, then cross-references later sessions in the same project. Each item is classified as resolved, orphaned, or unknown based on evidence found.

A Summary.md rollup is proposed for any project with 3 or more sessions that lacks an existing summary file. The summary includes a timeline table, key outcomes per session, current status, and carried-forward unresolved items.

No, the audit phase only reports findings and proposed actions. Renames, frontmatter fixes, status updates, and rollup generation execute only after you approve all or selected items from the numbered proposal list.