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.
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.