Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/technical-change-tracker
Track code changes with structured JSON records, state machine enforcement, and AI session handoff for bot continuity
Passed 19 of 24 test cases with the skill, and 8 of 24 without it.
and 12 more in the full report
13 fixed7 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are starting a new project folder and want to set up the change tracking directory and default configuration for the first time. Which command initializes the tracking environment?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies using the `/tc init` command. | Missed | Passed |
The instructions your model reads when the skill loads.
Track every code change with structured JSON records and accessible HTML output. Ensures AI bot sessions can resume seamlessly when previous sessions expire or are abandoned.
planned -> in_progress -> implemented -> tested -> deployed
|
+-> blocked
/tc init | /tc create | /tc update | /tc status | /tc resume | /tc close | /tc export | /tc dashboard | /tc retro
Each TC stores: progress summary, next steps, blockers, key context, and files in progress — so the next bot session picks up exactly where the last left off.
TC bookkeeping runs via background subagents. Never interrupts coding work.
test cases passed, vs 8 / 24 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.