technical-change-tracker

Track code changes with structured JSON records and HTML output.

Updated Aug 19, 2025
One-click install
npx skills add https://github.com/hoainam183/GR --skill technical-change-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-change-tracker
Source: https://github.com/hoainam183/GR/tree/main/src/RAG_v2/frontend/chat-companion/.agent/skills/technical-change-tracker
Command: npx skills add https://github.com/hoainam183/GR --skill technical-change-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining a structured record of code changes, ensuring seamless AI bot session handoff for uninterrupted work continuity.

Core Features & Use Cases

  • Structured Change Tracking: Tracks every code change with JSON records and accessible HTML output.
  • Session Handoff: Enables AI bot sessions to resume seamlessly after expiration or abandonment.
  • Use Case: Ideal for onboarding projects with undocumented change history or when a bot session needs to pick up where it left off.

Quick Start

Use the technical-change-tracker skill to initialize tracking for a new code change 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 track code changes with structured JSON records for development workflows?

Track code changes by initializing the technical-change-tracker to generate structured JSON records for each modification. It documents change history and outputs accessible HTML, ensuring development workflows maintain accurate modification logs.

How do I resume an AI bot session after it expires or gets abandoned?

Resume an AI bot session by utilizing the session handoff feature to restore continuity. It enables the bot to pick up exactly where the previous session left off, preventing work loss after expiration or abandonment.

What is the best way to enforce a state machine during code change tracking?

Enforce a state machine during change tracking by using technical-change-tracker's built-in enforcement capabilities. This ensures code modifications follow valid state transitions, providing structured history documentation and process compliance.

Can I use technical-change-tracker to onboard projects with undocumented change history?

Yes, you can use technical-change-tracker to onboard projects lacking documentation. It initializes tracking to establish a structured JSON-based change history, making it ideal for retroactively documenting modifications and preparing for AI session handoffs.

How do I start tracking a new code change with technical-change-tracker?

Start tracking a new code change by running the '/tc init' command. This initializes the tracking process, creating structured JSON records that document modifications and support seamless AI bot session continuity.