Tc Tracker

Tracks code changes with structured JSON records, enforced state machines, and session handoff formats. Use when documenting technical changes, creating audit trails, managing change lifecycles, or handing off in-progress work between AI sessions.

skills.sh installs: 544
GitHub stars: 29.5K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add alirezarezvani/claude-skills --skill tc-tracker --agent claude-code

Installs into .claude/skills of the current project.

Files

TC Tracker

Track every code change with structured JSON records, an enforced state machine, and a session handoff format that lets a new AI session resume work cleanly when a previous one expires.

Overview

A Technical Change (TC) is a structured record that captures what changed, why it changed, who changed it, when it changed, how it was tested, and where work stands for the next session. Records live as JSON in docs/TC/ inside the target project, validated against a strict schema and a state machine.

Use this skill when the user:

Asks to "track this change" or wants an audit trail for code modifications
Wants to hand off in-progress work to a future AI session
Needs structured release notes that go beyond commit messages
Onboards an existing project and wants retroactive change documentation
Asks for /tc init, /tc create, /tc update, /tc status, /tc resume, or /tc close