Menu
Use when creating a branch, starting work on an issue, or checking out a new feature branch. Validates branch naming and links to GitHub issues automatically.
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
Use when committing changes, staging files, saving work, or making a git commit. Creates clean commits in the repository's own convention (conventional commits, area prefix, tracker ID, or plain) with secret scanning (GitLeaks).
Use when opening a PR, submitting for review, pushing a branch, or creating a pull request. Pushes and creates GitHub PRs with auto-assignment and description.
Use when hardening a dependency supply chain, pinning versions, adding registry/security flags, or setting up Renovate. Detects the language and locks down install scripts, versions, and CI checks (JS/TS, Python, Go, Rust).
Use when adding CI/CD, creating workflows, auditing GitHub Actions, or fixing action pinning. Creates and audits workflows for SHA pinning and permissions.
Use when filing a bug, requesting a feature, creating an issue, or updating issue details. Manages issues on GitHub (and GitLab via glab) with templates, formatting, and auto-assignment.
Use when reviewing file names, renaming files, fixing naming conventions, or auditing exports. Enforces consistent casing and suffix patterns.
| name | create-branch |
| description | Use when creating a branch, starting work on an issue, or checking out a new feature branch. Validates branch naming and links to GitHub issues automatically. |
| license | MIT |
| allowed-tools | Read Bash(git:*) Bash(gh:*) Bash(glab:*) |
| model | haiku |
| effort | low |
| compatibility | Requires git; issue-linking uses a GitHub (gh) or GitLab (glab) remote |
| metadata | {"short-description":"Validated branch names linked to issues."} |
You create and checkout git branches with validation.
Read individual rule files in rules/ for detailed requirements and examples.
| Rule | Impact | File |
|---|---|---|
| Branch naming | HIGH | rules/branch-naming.md |
| Prefix detection | MEDIUM | rules/prefix-detection.md |
git remote get-url origin (github.com → gh, gitlab.com → glab; default GitHub). On GitHub, use gh issue develop <number> -c to create a linked branch and skip to step 4. On GitLab (no direct equivalent), include the issue number in the branch name (e.g. feature/123-description) so the MR auto-links, then continue through steps 2–4rules/prefix-detection.md), validate name (see rules/branch-naming.md), and check for duplicates locally and remotelymain → master → current HEAD: git checkout -b <name> <base>git push -u origin <name>