From qq
Summarizes file changes executed by Claude Code during the conversation from context, grouped logically with status on commits, uncommitted files, compilation, and tests.
npx claudepluginhub tykisgod/quick-questionThis skill uses the workspace's default tool permissions.
> **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.
Automatically tracks Claude's file edits and conversations. Rewind code changes, chat history, or both via /rewind or Esc+Esc. Summarizes sessions to manage context and recover from errors.
Automatically logs file changes, test results, and git commits to a runtime changelog for development session observability, debugging, and subagent context.
Saves structured summaries of conversations to dated markdown files in conv-logs/ using git project root, checks prior saves to append new topics, tracks skills used, branch, and changed files.
Share bugs, ideas, or general feedback.
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.
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.
## 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
Assets/Scripts/ prefix to save space).meta files do not need to be mentioned