session-review

Audit changed Markdown files for stale task references before commit using tcli queries.

Updated Jan 20, 2026

Search Tags:#git #markdown #consistency #audit #readme #status #task

Ready to run

npx skills add https://github.com/vogon101/KnowledgeWork --skill session-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-review
Source: https://github.com/vogon101/KnowledgeWork/tree/main/skills/session-review
Command: npx skills add https://github.com/vogon101/KnowledgeWork --skill session-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps QA and developers ensure task references in changed notes are up-to-date with the database before committing.

Core Features & Use Cases

Detects changed Markdown files, extracts task IDs like T-<digits>, batches queries the current statuses via tcli, and flags mismatches.
Presents actionable findings and suggested fixes for user approval.
Use case: end-of-session review before pushing changes to the repository.

Quick Start

Navigate to your content directory.
Run git diff --name-only to identify modified files.
Run the session-review workflow to audit task references and prepare fixes.

Frequently Asked Questions about session-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check Markdown files for stale task references before a git commit?▼

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.

How does task reference auditing work for modified notes?▼

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.

Can I verify README frontmatter statuses against my task database?▼

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.

Do I need tcli to audit task IDs in Markdown files?▼

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.

What is the best way to prevent outdated task statuses from being pushed to a repository?▼

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.