Complete AI Training
Sign inBecome a member

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Skill · Development

Technical change tracker

Track code changes with structured JSON records, state machine enforcement, and AI session handoff for bot continuity

Agentic Awesome SkillsAdded Sep 5, 2026
Use it in my AI

How to use it

  1. Start your plan and connect your AI once
  2. Add the skill to your AI, one time only: press Copy skill and paste it into your AI's instructions: a project in ChatGPT, Claude or Grok, a Gem in Gemini, an agent in Microsoft 365 Copilot, or a rule in Cursor. It stays there for every new chat. In Kimi, paste it at the start of a new chat.
  3. Ask for the task in your own words, or say it directly:
Use the Technical change tracker skill to help me with this.
SKILL.md

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 with status filters
  • Python stdlib only — zero external dependencies
  • Retroactive bulk creation from git history via /tc retro

Full Repository

https://github.com/Elkidogz/technical-change-skill — MIT License

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.