Individual skill

tc-tracker

Use when tracking technical changes as records, or handing work between AI sessions with a change record. Creates, updates and validates change records with tc_create.py, tc_update.py and tc_validator.py.

engineering/skills/tc-tracker/SKILL.md

Read pinned source

Source commit 9ef0c3c213932e645cc5cbeeb3c35c3a762a2437

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Network or broad shell
Last checked: Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 29,499
Repository last updated: Nov 5, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agentic-ai Repository topic
anthropic-claude Repository topic
claude-ai Repository topic
claude-code Repository topic
claude-skills Repository topic
claude-code-skills Repository topic
ai-coding-agent Repository topic
claude-code-plugins Repository topic
developer-tools Repository topic
openai-codex Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

README.mddoc · 2,278 bytes
SKILL.mdcore · 10,291 bytes
SKILL.mdcore · 10,291 bytes
SKILL.mdcore · 10,291 bytes
SKILL.mdcore · 10,291 bytes
SKILL.mdcore · 10,291 bytes
SKILL.mdcore · 10,291 bytes
references/handoff-format.mddoc · 5,291 bytes
references/lifecycle.mddoc · 4,037 bytes
references/tc-schema.mddoc · 5,386 bytes
scripts/tc_create.pyruns · 9,936 bytes
scripts/tc_init.pyruns · 6,861 bytes
scripts/tc_status.pyruns · 7,335 bytes
scripts/tc_update.pyruns · 14,181 bytes
scripts/tc_validator.pyruns · 14,226 bytes

Read excerpt


# 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`