session-review

To check Markdown files for stale task references before a git commit, you run a session review that scans changed files, extracts task IDs like T-123, and flags mismatches against current database statuses. It then presents actionable edits for your approval.

Task reference auditing works by detecting changed Markdown files, extracting task IDs formatted as T-<digits>, and batch-querying their current statuses via tcli. It verifies README frontmatter statuses against the database and highlights any mismatches.

Yes, you can verify README frontmatter statuses against your task database. The review process queries current statuses via tcli and flags any mismatches between the frontmatter values and the actual database records before you push changes.

Yes, you need tcli to audit task IDs in Markdown files. The workflow relies on tcli to batch-query the current statuses of extracted task IDs and compare them against the references found in your modified Markdown notes.

The best way to prevent outdated task statuses from being pushed is to perform an end-of-session review that audits modified files, batch-queries statuses via tcli, and presents actionable fixes for user approval before committing.