New Branch
- 5 installs
- 5 repo stars
- Updated August 5, 2026
- bjornmelin/dev-skills
new-branch is a skill that creates a conventional-commit, semver-compliant git branch first and then presents the full execution plan in chat.
About
This skill creates and switches to a new conventional-commit and semver-compliant git branch before any work begins. Developers use it when they want a scoped branch prepared first and a clear plan laid out in chat. It stops after switching branches unless asked to implement, then presents the intended changes, key files, verification, commit shape, and risks.
- Creates and checks out a conventional-commit, semver-compliant branch first
- Stops after switching branch unless implementation is requested
- Presents the full change, key files, verification, and PR plan in chat
New Branch by the numbers
- 5 all-time installs (skills.sh)
- Ranked #473 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
new-branch capabilities & compatibility
- Capabilities
- planning
- Use cases
- planning
What new-branch says it does
Create and switch to a new conventional-commit and semver-compliant branch before doing any work
Stop after switching to the new branch unless the user separately asks for implementation work.
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.
npx skills add https://github.com/bjornmelin/dev-skills --skill new-branchAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 5 |
|---|---|
| repo stars | ★ 5 |
| Last updated | August 5, 2026 |
| Repository | bjornmelin/dev-skills ↗ |
What it does
Preparing a scoped conventional-commit branch before work and presenting the change and PR plan in chat.
Who is it for?
Developers who want a scoped branch prepared and a plan laid out before implementation.
Skip if: Doing the implementation itself; it stops after switching branches unless asked.
When should I use this skill?
The user wants a branch prepared first and a clear plan in chat before implementation.
By the numbers
- 4-step branch-then-plan workflow
Files
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.
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148