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".
npx claudepluginhub month2month/m2m-developer-plugin --plugin m2m-developerThis skill is limited to using the following tools:
Create a new branch from an up-to-date default branch, ready for development.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Guides TDD-style skill creation: pressure scenarios as tests, baseline agent failures, write docs to enforce compliance, verify with RED-GREEN-REFACTOR.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
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)