skills.rest
Wladimirfn
WladimirfnCOMMUNITY
Explore all skills by this author →
GitHub

technical-change-tracker

Track code changes in structured JSON records during AI coding sessions.

Updated May 23, 2026
Search Tags:#accessibility#state machine#code tracking#AI session continuity#structured data logging
One-click install
npx skills add https://github.com/Wladimirfn/IDU-PI --skill technical-change-tracker-wladimirfn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: technical-change-tracker
Source: https://github.com/Wladimirfn/IDU-PI/tree/main/.agents/skills/technical-change-tracker
Command: npx skills add https://github.com/Wladimirfn/IDU-PI --skill technical-change-tracker-wladimirfn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill addresses the challenge of tracking code changes in AI coding sessions, enabling seamless handoff when sessions expire or are abandoned, and provides a comprehensive view of code evolution without extensive documentation.

Core Features & Use Cases

  • Structured Code Tracking: Keeps track of all code changes in structured JSON records for append-only history.
  • State Machine Management: Facilitates tracking the code change lifecycle from planned to deployed.
  • AI Session Handoff: Allows AI bot sessions to resume tasks exactly where they left off.
  • Accessibility: Provides WCAG AA+ accessible HTML output for easy understanding.
  • Use Case: A software development team uses this skill to ensure they have a clear trail of code changes, especially beneficial when switching between AI coding sessions or team members.

Quick Start

Initiate the tracking process with the command: /tc init

Frequently Asked Questions about technical-change-tracker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain AI session continuity for code tracking when a session expires?▼

AI session continuity is maintained by logging structured code changes in append-only JSON records, allowing bot sessions to resume tasks exactly where they left off after breaks.

How do I track code changes across a state machine lifecycle during development?▼

You can track code changes across a state machine lifecycle using structured JSON logging that records the evolution of code from planned states through to deployed states.

What is the best way to log structured data for code evolution in collaborative environments?▼

The best way to log structured data for code evolution is using append-only JSON records, which provide a comprehensive history trail without requiring extensive manual documentation.

Can I get accessible HTML output for code change logs to meet WCAG AA standards?▼

Yes, you can get accessible HTML output meeting WCAG AA+ standards, which makes understanding the structured code tracking records easier for all team members.

How do I initialize code change tracking for my development team?▼

You initialize code change tracking by running the /tc init command, which sets up the environment to start logging structured data for your collaborative development workflow.

Related Skills

Explore More Software Engineering Skills→
yocxy2yocxy2

context-restore

Restore session context and workspace state for multi-session engineering tasks.

Community
Intermediate
PaddlePaddlePaddlePaddle
3.7k

benchmark

Benchmark FastDeploy versus SGLang with end-to-end tests and HTML reports.

Official
Advanced
SensLiaoSensLiao

gsd-pause-work

Detect current code phase and save work state via file and Git commits.

Community
Basic
hoainam183hoainam183

technical-change-tracker

Track code changes with structured JSON records and HTML output.

Community
Intermediate