technical-change-tracker
Track code changes with structured JSON records, state machine enforcement, and AI session handoff for bot continuity
Profile →npx skills add sickn33/agentic-awesome-skills --skill technical-change-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.
# Technical Change Tracker ## Overview 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. ## When to Use This Skill - Use when you need structured change tracking across AI coding sessions - Use when a bot session expires mid-task and the next session needs full context to resume - Use when onboarding a project with undocumented change history ## How It Works ### State Machine ``` planned -> in_progress -> implemented -> tested -> deployed | +-> blocked ``` ### Commands `/tc init` | `/tc create` | `/tc update` | `/tc status` | `/tc resume` | `/tc close` | `/tc export` | `/tc dashboard` | `/tc retro` ### Session Handoff 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. ### Non-Blocking TC bookkeeping runs via background subagents. Never interrupts coding work. ## Features - Structured JSON records with append-only revision history - Test cases with log snippet evidence - WCAG AA+ accessible HTML output (dark theme, rem-based fonts) - CSS-only dashboard w
- Overview
- When to Use This Skill
- How It Works
- State Machine
- Commands
- Session Handoff
- Non-Blocking
- Features
- Full Repository
- Limitations
What does the technical-change-tracker skill do?
Track code changes with structured JSON records, state machine enforcement, and AI session handoff for bot continuity
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill technical-change-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 sickn33/agentic-awesome-skills, a repository with 44,414 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.