domains / families / software-engineering / technical-change-tracker
technical-change-tracker
authentic
Track code changes with structured JSON records, state machine enforcement, and AI session handoff for bot continuity
When to use
- 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
When not to use
- 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.
Skill page
Source