What it does
This skill creates a branch from main to start work in a GitHub repository. It chooses a prefix based on the type of change: feat, fix, docs, ci, chore, or refactor, followed by a short kebab-case name. For example, feature work can use feat/add-agentic-rerank, while a bug fix can use fix/empty-profile-crash.
Before creating the branch, it switches to main and updates it, then creates the new working branch from that state. Each branch should have one purpose. After the work, the flow is to open a pull request back to main; the skill assumes contributors do not commit directly to main.
When it helps
Use it when starting a feature, bug fix, documentation update, or another distinct type of change. It is also useful when you want branch names to follow a consistent convention across a repository.
Example requests
- “Create a branch for adding a setting to the settings screen.”
- “Create a branch to fix the crash with an empty profile.”
- “Create a branch for updating the development guide.”
Notes
This skill requires Git and a GitHub repository. It updates main before creating the new branch.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.