From superartes
Use when starting feature work that needs isolation from the main branch or before executing implementation plans - creates a feature branch with safety verification
How this skill is triggered — by the user, by Claude, or both
Slash command
/superartes:using-feature-branchesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a feature branch to isolate work from the main branch before starting implementation.
Create a feature branch to isolate work from the main branch before starting implementation.
Core principle: Branch from clean base + verify test baseline = reliable isolation.
Announce at start: "I'm using the using-feature-branches skill to set up an isolated branch."
git status
If uncommitted changes exist: Ask the user how to handle them (stash, commit, or discard) before proceeding.
# Identify the main branch
git branch -l main master 2>/dev/null
If ambiguous, ask the user which branch to base the feature on.
# Update base branch
git checkout <base-branch>
git pull
# Create and switch to feature branch
git checkout -b <feature-branch-name>
Branch naming: Use descriptive names like feature/auth-system, fix/login-timeout, refactor/db-layer. Ask the user if no name is obvious from context.
Auto-detect and run appropriate setup if dependencies may be out of date:
# Node.js
if [ -f package.json ]; then npm install; fi
# Rust
if [ -f Cargo.toml ]; then cargo build; fi
# Python
if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
if [ -f pyproject.toml ]; then poetry install; fi
# Go
if [ -f go.mod ]; then go mod download; fi
Run tests to ensure the branch starts clean:
# Use project-appropriate command
npm test / cargo test / pytest / go test ./...
If tests fail: Report failures, ask whether to proceed or investigate.
If tests pass: Report ready.
Feature branch ready: <branch-name> (based on <base-branch>)
Tests passing (<N> tests, 0 failures)
Ready to implement <feature-name>
| Situation | Action |
|---|---|
| Uncommitted changes | Ask user (stash/commit/discard) |
| Base branch unclear | Ask user |
| Tests fail during baseline | Report failures + ask |
| No package.json/Cargo.toml | Skip dependency install |
git status before branchinggit pull on base branch before creating feature branchNever:
Always:
Called by:
Pairs with:
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub andybrandt/superartes --plugin superartes