tc-tracker
Use when the user asks to track technical changes, create change records, manage TC lifecycles, or hand off work between AI sessions. Covers init/create/update/status/resume/close/export workflows for structured code change documentation.
Profile →npx skills add alirezarezvani/claude-skills --skill tc-tracker --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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` **Do NOT use this skill when:** - The user only wants a changelog from git history (use `engineering/changelog-generator`) - The user only wants to track tech debt items (use `engineering/tech-debt-tracker`) - The change is trivial (typo, formatting) and won
- Overview
- Storage Layout
- TC ID Convention
- State Machine
- Workflow Commands
- 1. Initialize tracking in a project
- 2. Create a new TC record
- 3. Update a TC record
- 4. View status
- 5. Validate a record or registry
- Slash-Command Dispatcher
- Session Handoff Format
- Validation Rules (Always Enforced)
- Non-Blocking Bookkeeping Pattern
python3 scripts/tc_init.py --project "My Project" --root . python3 scripts/tc_create.py \ Status transition (validated against the state machine) python3 scripts/tc_update.py --root . --tc-id TC-001-04-05-26-user-auth \ Add a file Append handoff data Single TC python3 scripts/tc_status.py --root . --tc-id TC-001-04-05-26-user-auth All TCs (registry summary) python3 scripts/tc_status.py --root . --all --json
What does the tc-tracker skill do?
Use when the user asks to track technical changes, create change records, manage TC lifecycles, or hand off work between AI sessions. Covers init/create/update/status/resume/close/export workflows for structured code change documentation.
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill tc-tracker --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.