Menu
Generate structured changelogs for app releases from git history. Use when preparing releases, documenting changes, or creating version notes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Update llms.md documentation for LLM consumption based on codebase changes. Use when adding providers, changing APIs, updating types, or when the LLM reference guide drifts from implementation.
Update and reorganize README documentation based on codebase changes. Use when adding features, refactoring modules, updating APIs, or when documentation drifts from implementation.
Comprehensive multi-agent code review with parallel analysis. Use for thorough code reviews, finding bugs, checking regressions, or getting alternative implementation perspectives.
Review feature implementations for spec compliance, code quality, and organizational consistency. Use when implementing features, checking spec compliance, validating API implementations, or preparing releases.
| name | changelog-generator |
| description | Generate structured changelogs for app releases from git history. Use when preparing releases, documenting changes, or creating version notes. |
| allowed-tools | Read, Bash(git:*) |
Generate clean, developer-friendly changelogs from git history with code samples for breaking changes.
# Find the last release tag
git describe --tags --abbrev=0
# List recent tags for reference
git tag --sort=-version:refname | head -5
# Get commits since last tag
git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-merges
Create .changelogs/{version}.md with:
# v{version}
## Changes
- [ ] Added: Feature description
- [ ] Fixed: Bug description
- [ ] Changed: Behavior change description
- [ ] Removed: Deprecated item
## Breaking Changes
### Change Title
Brief description of what changed.
```ts
// Before
oldMethod(param: string)
// After
newMethod(param: string, options?: Options)
[Only if applicable - brief migration steps]
## Guidelines
- **Group by type**: Added, Fixed, Changed, Removed, Deprecated
- **Be concise**: One line per change, details only when needed
- **Code samples**: Only for developer-facing changes that need examples
- **Language tags**: Always include language in code blocks (e.g., `ts`, `js`, `bash`)
## Example
**Input**: Generate changelog for v2.1.0
**Output**: `.changelogs/v2.1.0.md`
```markdown
# v2.1.0
## Changes
- [x] Added: WebSocket reconnection with exponential backoff
- [x] Fixed: Memory leak in event listener cleanup
- [x] Changed: Default timeout from 30s to 60s
## Breaking Changes
### Event handler signature updated
```ts
// Before
client.on('message', (data) => {})
// After
client.on('message', (data, metadata) => {})
## Notes
- Infer version from context or prompt user if unclear
- Skip merge commits and version bump commits
- Focus on user/developer-facing changes