القائمة
Generate GitHub release notes from commits since the last git tag, then create a GitHub release. Use when the user wants to cut a release, create release notes, or publish a new version.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create a GitHub pull request from the current branch with a concise title and brief body. Use when the user wants Codex to open, draft, or prepare a PR for the current branch. Default to a draft PR unless the user explicitly asks for a ready-for-review PR. If the branch name contains a Linear-style issue key such as `eng-1234`, prefix the PR title with `[eng-1234]: `. Keep the description concise, omit a Testing section unless requested, and add a Why section only when it can be inferred from the change without fluff.
Recompute local Codex and Claude/Claude Code monthly token usage and API-rate pricing from ~/.codex and ~/.claude logs. Use when the user asks for AI usage, token totals, monthly pricing tables, Codex usage, Claude Code usage, Claude inference usage, or a rerun of prior usage/cost reports.
Stage all tracked and untracked repository changes and create a git commit with a concise, high-signal message. Use when the user wants Codex to commit current work, prepare a clean checkpoint, or write a commit message from the staged or unstaged diff. Always enforce a commit subject of 88 characters or fewer and add a body only when the change is complex enough to need extra context.
Use when the user asks to review a plan, critique a plan, or wants feedback on an implementation plan before writing code. Triggers on "review this plan", "plan review", "/plan-review", or similar requests to evaluate a proposed approach.
| name | release-notes |
| description | Generate GitHub release notes from commits since the last git tag, then create a GitHub release. Use when the user wants to cut a release, create release notes, or publish a new version. |
| argument-hint | ["tag-name"] |
| allowed-tools | Bash(git *), Bash(gh *) |
You are creating a GitHub release. Follow these steps:
Run these commands to understand the current state:
git tag --sort=-version:refname | head -5
to see recent tags, then:
git log <last-tag>..HEAD --oneline --no-merges
to get all commits since the last tag. Also run:
git log <last-tag>..HEAD --pretty=format:"%s" --no-merges
for cleaner commit messages.
Organize the commits into a clean GitHub release message using this structure, summarizing and grouping them where appropriate to get the point accross:
## What's Changed
### Features
- ...
### Bug Fixes
- ...
### Improvements
- ...
### Other Changes
- ...
Only include sections that have relevant commits. Keep bullet points concise and human-readable — rewrite terse commit messages into plain English where needed. Omit chore/maintenance commits (dependency bumps, formatting, etc.) unless notable. If a bunch of commits are related, group them into a single message.
Ask the user to provide the tag name.
Display the full release command that will be run, including the tag and release notes, and ask the user to confirm before creating the release.
Once confirmed, run:
gh release create <tag> --title "<tag>" --notes "<release notes>"
If creating a draft first is preferred, add --draft.
After creating, output the release URL.