Summarize all changes Claude Code made during this conversation.
Scanned 5/27/2026
Install via CLI
openskills install tykisgod/quick-question---
description: "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.
## 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:
```bash
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"
No comments yet. Be the first to comment!
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.
Python backend development expertise for FastAPI, security patterns, database operations, Upstash integrations, and code quality. Use when: (1) Building REST APIs with FastAPI, (2) Implementing JWT/OAuth2 authentication, (3) Setting up SQLAlchemy/async databases, (4) Integrating Redis/Upstash caching, (5) Refactoring AI-generated Python code (deslopification), (6) Designing API patterns, or (7) Optimizing backend performance.
Drive the full internationalization journey for a project — detect the stack, recommend a library, set up the chosen library, wrap existing strings, and optionally connect a translation platform. Use when the user asks to add or configure i18n, internationalization, localization, multi-language support, or translations — including when they explicitly mention LinguiJS, Lingui, next-intl, "wrap strings", "find hardcoded text", "make my app translatable", or "set up translations". Triggers on g...
PTES-aligned adversarial security audit for backend, frontend, and mobile applications. Produces a CVSS-scored Hacker Report with verified PoCs and phased remediation.