# New Branch

> Create and switch to a conventional-commit branch before any work starts, then present the branch and PR plan in chat before implementing. Use when the user wants the branch prepared first and the plan agreed up front.

- Skill: `bjornmelin/new-branch` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add bjornmelin/new-branch`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bjornmelin/new-branch/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: BjornMelin (https://skillmd.com/u/bjornmelin)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/bjornmelin/new-branch

---


# New Branch

1. Before any other work, inspect the current branch/worktree state.
2. Create and checkout a new branch for the task using a conventional-commit and semver-compliant name, keeping it short and scoped, for example `feat/add-x`, `fix/y`, or `chore/z`.
3. Stop after switching to the new branch unless the user separately asks for implementation work.
4. In chat, provide the complete plan for work to be done on that branch and its pull request: intended changes, key files, verification, commit shape, and any risks or blockers.