How do I install the Changes skill?

Run npx skillmds@latest add tykisgod/changes in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Changes skill do?

Summarize all changes Claude Code made during this conversation. It is listed under Research & Search on SkillMD.

Is Changes safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Changes?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Changes free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Changes?

tykisgod (@tykisgod) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Changes by tykisgod — Agent Skill

Name: Changes
Author: tykisgod

File contents

Script path fallback: qq scripts are invoked as bare commands (e.g. unity-test.sh). If "command not found", use ${CLAUDE_PLUGIN_ROOT}/bin/<command> instead.

Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md).

Summarize all changes Claude Code made during this conversation.

Behavior

Review the current conversation context and identify all file changes actually executed by Claude in this conversation (file modifications made via Edit/Write/Bash tools), then summarize them grouped by logic.

The data source is the conversation context, not git diff. The user may have gone through multiple rounds of changes in a single conversation — some already committed, some not. Summarize all of them.

After producing the summary, if qq-run-record.py is available, persist a changes run record so controller state can advance:

qq-run-record.py record \
  --project . \
  --stage changes \
  --command qq:changes \
  --status checked \
  --summary "Conversation change summary captured" \
  --capture-local-changes

Only do this after the summary is complete.

Output format

## Summary of changes in this conversation

### <Group 1 title>
- What was done
- Key files: ...

### <Group 2 title>
- ...

### Status
- Committed: <list of commit hashes, if any>
- Uncommitted: <list of files, if any>
- Compilation: passed / not verified
- Tests: N/N passed / not run

Notes

List the main file paths for each group (omit the Assets/Scripts/ prefix to save space)
If there are architectural changes (file moves, namespace changes, asmdef changes), call them out separately
.meta files do not need to be mentioned
If there were multiple rounds of changes in the conversation (e.g., did A first, then changed B), group them in chronological order
If any changes were rolled back or overwritten, show only the final state, but note "tried X then changed to Y"

---name: changesdescription: Summarize all changes Claude Code made during this conversation.---> **Script path fallback**: qq scripts are invoked as bare commands (e.g. `unity-test.sh`). If "command not found", use `${CLAUDE_PLUGIN_ROOT}/bin/<command>` instead.Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md).Summarize all changes Claude Code made during this conversation.## BehaviorReview the current conversation context and identify all **file changes actually executed** by Claude in this conversation (file modifications made via Edit/Write/Bash tools), then summarize them grouped by logic.**The data source is the conversation context, not git diff.** The user may have gone through multiple rounds of changes in a single conversation — some already committed, some not. Summarize all of them.After producing the summary, if `qq-run-record.py` is available, persist a `changes` run record so controller state can advance:```bashqq-run-record.py record \ --project . \ --stage changes \ --command qq:changes \ --status checked \ --summary "Conversation change summary captured" \ --capture-local-changes```Only do this after the summary is complete.## Output format```## Summary of changes in this conversation### <Group 1 title>- What was done- Key files: ...### <Group 2 title>- ...### Status- Committed: <list of commit hashes, if any>- Uncommitted: <list of files, if any>- Compilation: passed / not verified- Tests: N/N passed / not run```## Notes- List the main file paths for each group (omit the `Assets/Scripts/` prefix to save space)- If there are architectural changes (file moves, namespace changes, asmdef changes), call them out separately- `.meta` files do not need to be mentioned- If there were multiple rounds of changes in the conversation (e.g., did A first, then changed B), group them in chronological order- If any changes were rolled back or overwritten, show only the final state, but note "tried X then changed to Y"

Frequently asked questions

Changes