changes

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.