changes

Compile a summary of all file modifications from Claude Code conversation context.

10|2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/tykisgod/quick-question --skill changes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changes
Source: https://github.com/tykisgod/quick-question/tree/main/skills/changes
Command: npx skills add https://github.com/tykisgod/quick-question --skill changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Iterating on code with Claude Code often involves dozens of small edits, writes, and bash commands across a single conversation, making it hard to track all changes, distinguish between committed and uncommitted work, and identify architectural modifications. This skill automates compiling a clear, organized summary of all executed changes, removing the need for manual tracking or relying solely on git diff.

Core Features & Use Cases

  • Automated Change Detection: Pulls all file modifications directly from conversation context (Edit, Write, Bash tool actions) without requiring git diff as the only data source.
  • Logical Grouping & Highlighting: Organizes changes by chronological order and logical purpose, with explicit callouts for architectural changes like file moves, namespace updates, or asmdef adjustments.
  • Run Record Support: Optionally saves a changes run record via qq-run-record.py to advance controller state when the script is available in the project environment. Use Case: After a 2-hour session of iterating on a Unity player controller script, run this skill to get a structured summary of all modified files, committed vs uncommitted status, compilation results, and test outcomes in seconds.

Quick Start

Use the changes skill to generate a complete summary of all file modifications Claude Code made during this conversation.

Frequently Asked Questions about changes

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

FAQPage Schema
How do I track all file modifications made by Claude Code in a single conversation?

Track file modifications by compiling a complete summary of all edits, writes, and bash operations executed during a single conversation. This automated change detection organizes modifications by chronological order and logical purpose without relying solely on git diff.

What is the best way to summarize uncommitted code changes from an iterative game development session?

Summarize uncommitted code changes by extracting file modifications directly from the conversation context, tracking both committed and uncommitted work. This provides a structured summary of modified files, architectural modifications, and test outcomes for iterative game development workflows.

Can I track architectural changes and file moves without relying exclusively on git diff?

Track architectural changes and file moves by pulling modification data directly from Claude Code's conversation context. This approach highlights structural modifications like namespace updates and asmdef adjustments, satisfying version control requirements without using git diff as the only data source.

Does this change tracking approach work with Unity, Godot, Unreal, and S&box projects?

This change tracking approach works with Unity, Godot, Unreal, and S&box projects. It applies to iterative game development workflows where multiple rounds of edits, writes, and bash operations are performed in a single session across these engines.

How do I generate a run record for compilation results and test outcomes after a coding session?

Generate a run record for compilation results by optionally saving a changes run record via the qq-run-record.py script. This advances controller state and provides a structured summary of modified files, committed vs uncommitted status, and test outcomes when the script is available in the project environment.