Skill12.9k repo starsupdated 2d ago

new-branch

The new-branch skill automates branch creation within EverOS's GitFlow Lite model, determining whether to cut feature, fix, or hotfix branches from the appropriate parent (dev or master), pulling latest changes, and establishing properly named branches in kebab-case format. Use this when starting new development work to ensure branches follow the project's structured workflow and integrate correctly through pull requests.

View source Repository: EverOS

Install in Claude Code

Copy

git clone --depth 1 https://github.com/EverMind-AI/EverOS /tmp/new-branch && cp -r /tmp/new-branch/.claude/skills/new-branch ~/.claude/skills/new-branch

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

# /new-branch

Cut a new branch for the GitHub repository.

## Branch model

```
main       = default and protected branch
feat/*     = feature work
fix/*      = bug fixes
docs/*     = documentation-only changes
ci/*       = CI, build, and developer-experience changes
chore/*    = repository maintenance
refactor/* = behavior-preserving code structure changes
```

## Steps

1. Ask (or infer) the change type: `feat`, `fix`, `docs`, `ci`, `chore`, or
   `refactor`.
2. Update `main` first:
   ```bash
   git checkout main
   git pull --ff-only
   ```
3. Create the branch with a kebab-case slug:
   ```bash
   git checkout -b <type>/<short-slug>
   ```
4. Keep the branch scoped to one purpose and open a pull request back to
   `main`.

## Naming

- `feat/add-agentic-rerank`, `fix/empty-profile-crash`,
  `docs/quickstart-config`, `ci/check-github-docs`.
- Lowercase, hyphen-separated, no spaces, concise.

Never commit directly to `main` — always use a branch and pull request.