Menu
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.
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
Generate a changelog or release notes from recent git history. Use when asked to write a changelog, summarize recent commits, or produce release notes.
Scaffold a new custom SKILL.md file interactively. Use when asked to create a new skill or slash command.
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 | branch |
| description | 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. |
| allowed-tools | Bash |
Manage git branches for this repository.
Current branch state: !{git branch -a 2>/dev/null | head -20 || echo "(not a git repo)"}
Open issues (for branch naming): !{gh issue list --limit 10 --json number,title,state 2>/dev/null || echo "(gh CLI not available)"}
Task: $ARGUMENTS
Branch naming convention:
feature/<issue-number>-<short-slug> (e.g. feature/42-add-gh-skills)fix/<issue-number>-<short-slug> (e.g. fix/17-loop-on-empty-response)feature/<short-slug> or fix/<short-slug>Steps:
git checkout -b feature/42-add-gh-skillsgit branch --show-currentIf the branch already exists, switch to it: git checkout <branch-name>