Menu
Generate a changelog or release notes from recent git history. Use when asked to write a changelog, summarize recent commits, or produce release 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
Scaffold a new custom SKILL.md file interactively. Use when asked to create a new skill or slash command.
Create or switch to a feature branch, typically tied to a GitHub issue. Use when asked to create a branch or start work on an issue.
Create, view, list, or comment on GitHub issues. Use when asked to file, open, or manage GitHub issues.
Create, review, or manage GitHub pull requests. Use when asked to open, check, or merge a PR.
Run the linter, auto-fix what's fixable, and report the rest. Use when asked to lint or fix lint errors.
Run the project test suite and surface failures. Use when asked to run tests or check test status.
| name | changelog |
| description | Generate a changelog or release notes from recent git history. Use when asked to write a changelog, summarize recent commits, or produce release notes. |
| allowed-tools | Bash Read |
Generate a user-facing changelog grouped into Added / Changed / Fixed sections.
Recent git history: !{git log --oneline -30 2>/dev/null || echo "(no git history available)"}
Recent tags: !{git tag --sort=-creatordate 2>/dev/null | head -5 || echo "(no tags)"}
Scope: $ARGUMENTS
Steps:
v1.2.0..HEAD or a target version tag), run git log --oneline <scope> to get the relevant commits; otherwise use the recent history shown above.