菜单
Analyze git commits in a range by examining actual code diffs (not commit titles) and produce a ranked list of improvements and optimizations. Use when the user wants a changelog, wants to summarize recent changes, asks what changed since a commit, or wants to review project progress.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/msgbyte/cutia --skill changelog-analyzer命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | changelog-analyzer |
| description | Analyze git commits in a range by examining actual code diffs (not commit titles) and produce a ranked list of improvements and optimizations. Use when the user wants a changelog, wants to summarize recent changes, asks what changed since a commit, or wants to review project progress. |
Analyze all code changes between two git commits and produce a ranked summary of improvements and optimizations based on actual code diffs, not commit messages.
e0be0387a636a93a062cee621fd78b83dfccb06eHEADIf the user specifies a different range, use their values.
# List all commits in range (inclusive of start)
git log --oneline <start>~1..HEAD
# Get overall stats
git diff --stat <start>~1..HEAD
The diff may be very large. Process it in logical batches by directory or feature area:
# Get diff for a specific path
git diff <start>~1..HEAD -- <path>
# Or per-commit diffs when granularity matters
git show --stat <commit-hash>
git show <commit-hash> -- <file>
Key analysis areas (check each):
apps/web/src/components/ — UI components, UX improvementsapps/web/src/services/ — Service layer, storage, transcriptionapps/web/src/core/ and apps/web/src/lib/ — Core logic, utilitiesapps/web/src/hooks/ — React hooks, state managementapps/web/src/stores/ — Zustand stores, state architectureapps/web/src/types/ — Type definitions, data model changesapps/web/src/app/ — Pages, routes, API endpointspackages/ — Shared packagesFor each meaningful change found in the diffs, classify it into one of these categories:
| Category | Icon | Description |
|---|---|---|
| New Feature | ✨ | Entirely new capability added |
| Performance | ⚡ | Speed, memory, or rendering optimization |
| Bug Fix | 🐛 | Corrected broken or incorrect behavior |
| UX Improvement | 🎨 | Better user experience, UI polish |
| Refactor | ♻️ | Code restructuring without behavior change |
| Architecture | 🏗️ | Structural or design pattern improvement |
| DX / Tooling | 🔧 | Developer experience, build, CI/CD |
| i18n | 🌐 | Internationalization, localization |
| Security | 🔒 | Security hardening |
| Cleanup | 🧹 | Dead code removal, dependency cleanup |
Rate each change on impact (1-5):
| Score | Criteria |
|---|---|
| 5 | Core feature, affects most users, or prevents data loss |
| 4 | Significant feature or major UX/perf improvement |
| 3 | Notable improvement, moderate user impact |
| 2 | Minor enhancement, affects subset of users |
| 1 | Cosmetic, cleanup, or internal-only change |
Output a markdown report with this structure:
# Changelog: <start-hash-short>..<end-hash-short>
**Period**: <first-commit-date> → <last-commit-date>
**Commits**: <count> | **Files changed**: <count> | **+<insertions> / -<deletions>**
---
## Key Changes (by importance)
### ⭐⭐⭐⭐⭐ Critical / High Impact
#### ✨ [Feature/Change Title]
- **What changed**: Concise description based on actual code diff
- **Files**: List of key files modified
- **Impact**: Why this matters to users or the codebase
### ⭐⭐⭐⭐ Significant
...
### ⭐⭐⭐ Notable
...
### ⭐⭐ Minor
...
### ⭐ Cosmetic / Internal
...
---
## Summary Statistics
| Category | Count |
|----------|-------|
| New Features | X |
| Performance | X |
| Bug Fixes | X |
| ... | ... |
git diff or git show to see what really changed.