TC Tracker
TC Tracker creates structured JSON records for every code change, enforcing a strict state machine and append-only revision history. It produces a complete audit trail with session handoff data so a new AI session can resume work cleanly.
✨ What it does
- Enforces a state machine (planned -> in_progress -> implemented -> tested -> deployed) with valid transitions.
- Generates sequential TC IDs and maintains append-only revision history (R1, R2...) and test case IDs (T1, T2...).
- Validates records against a strict schema, including approval consistency (approved=true requires approved_by and approv
- Provides session handoff blocks with progress, next steps, blockers, and key context for AI continuity.
- Supports atomic writes and registry statistics recomputation.
- Includes Python scripts for init, create, update, status, and validation.
🎯 When to use it
- When the user asks to track a code change or wants an audit trail for modifications.
- When handing off in-progress work to a future AI session.
- When structured release notes beyond commit messages are needed.
- When onboarding an existing project and retroactive change documentation is required.
- When the user invokes /tc commands like init, create, update, status, resume, close, or export.
🚀 How to use
Trigger: /focused-fix
Trigger via slash commands like /tc init, /tc create , /tc update , /tc status, /tc resume, or /tc close, or by asking to track a change. Provide project root, change details (name, title, scope, priority, summary, motivation), and for updates specify status changes, files, or handoff data. Example prompts:
/tc create user-authentication --title "Add JWT auth" --scope feature --priority high
/tc update TC-001-04-05-26-user-auth --set-status in_progress --reason "Starting implementation"
📄 Output: Structured JSON records in docs/TC/ with a registry, config, and evidence directory.
📦 Add this skill to Claude Code
# 1. Get the skills repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills /tmp/claude-skills
# 2. Copy this skill into your project (or ~/.claude/skills for all projects)
mkdir -p .claude/skills
cp -r /tmp/claude-skills/engineering/skills/tc-tracker .claude/skills/tc-trackerSkill source: engineering/skills/tc-tracker/SKILL.md
⚠️ Good to know
Requires Python 3 and the target project directory; not for trivial changes or git-history-only changelogs.
❓ FAQ
What happens if I try to set a TC to 'deployed' without going through intermediate states?
The state machine validation will reject the transition; you must walk through in_progress -> implemented -> tested -> deployed.
Can I edit a revision history entry to fix a typo?
No, revision history is append-only; add a new revision that corrects the field instead.
What does the /tc resume command do?
It displays the handoff block for the TC, archives the prior session, and starts a new session context.
🤖 Overview, features, install steps and FAQ were generated from the project's SKILL.md on Sep 4, 2026. Always check the original source before running commands.