tc-tracker

Track code changes as Technical Changes with append-only revisions and session handoffs.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/Patasse97/claude-skills --skill tc-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tc-tracker
Source: https://github.com/Patasse97/claude-skills/tree/main/engineering/tc-tracker
Command: npx skills add https://github.com/Patasse97/claude-skills --skill tc-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Structured approach to documenting code changes as Technical Changes (TCs) to create an auditable history and enable reliable handoffs between AI sessions.

Core Features & Use Cases

  • Supports init, create, update, status, resume, close, and export workflows for code changes
  • Stores records in docs/TC with tc_record.json and tc_registry.json, enabling an immutable audit trail
  • Provides a session handoff format to resume work across AI sessions and teams

Quick Start

Initialize TC tracking in your project and create the first TC with a concise title.

Frequently Asked Questions about tc-tracker

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

FAQPage Schema
How do I track code changes with an immutable audit trail for my project?

You can track code changes by documenting them as Technical Changes (TCs) to establish an immutable audit trail. This method enforces a strict state machine and append-only revisions, storing records in your project's documentation directory.

What is the best way to document technical changes for AI session handoffs?

Documenting technical changes for AI session handoffs requires a structured format to enable seamless continuity. By logging immutable change records, you provide clear context that allows AI sessions to resume work instantly.

How do I initialize a change log and manage code change workflows?

You initialize a change log by setting up tracking in your project, then manage code change workflows across create, update, status, resume, close, and export states. This establishes a registry of technical changes with strict lifecycle management.

Can I export a technical change log for team collaboration?

Yes, you can export a technical change log using the export workflow. This allows your team to review the immutable history of code changes and utilize the structured handoff format for collaborative continuity.

Does this technical change tracking approach work without external dependencies?

Yes, this technical change tracking approach operates without external dependencies. It manages the audit trail and state machine natively using local scripts and references stored directly within your project.

Why use a strict state machine for code change documentation instead of a simple change log?

A strict state machine for code change documentation enforces append-only revisions and prevents unauthorized modifications, ensuring a reliable audit trail. This structured tracking guarantees data integrity for reliable session handoffs.