Stats
Actions
Tags
From m2m-developer
Create a fresh feature or fix branch from the latest default branch. Use when user wants to start new work on a clean branch, e.g. "create a branch for X", "start a new feature branch", "new branch for fixing Y".
How this skill is triggered — by the user, by Claude, or both
Slash command
/m2m-developer:create-feature-branchThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a new branch from an up-to-date default branch, ready for development.
Create a new branch from an up-to-date default branch, ready for development.
git status
If there are uncommitted changes (staged, unstaged, or untracked), warn the user and ask how to proceed. Suggest using the move-changes-to-branch skill if they want to bring changes along.
If $ARGUMENTS is provided, use it as or derive the branch name from it. Otherwise, ask the user what the branch is for.
Use conventional prefixes: feat/, fix/, chore/, refactor/, docs/.
DEFAULT_BRANCH=$(git remote show origin | grep 'HEAD branch' | awk '{print $NF}')
If git remote show origin fails (no remote configured), ask the user which branch to base off of.
git checkout $DEFAULT_BRANCH
git pull origin $DEFAULT_BRANCH
git checkout -b <new-branch-name>
Show:
git log --oneline -1)npx claudepluginhub month2month/m2m-developer-plugin --plugin m2m-developerCreates a feature branch or worktree before writing artifacts. Detects the base branch, infers a branch name from context, and confirms with the user.
Creates and switches to a new Git branch from an inline description, conversation context, or local diffs. Preserves uncommitted changes. Use for starting fresh or moving in-progress work to a named branch.
Creates git branches following Sentry naming conventions by analyzing changes and classifying branch types. Useful for standardizing branch creation.