CtrlK
BlogDocsLog inGet started
Tessl Logo

new-branch

Create a GitHub branch from main with the project naming convention

58

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/new-branch/SKILL.md
SKILL.md
Quality
Evals
Security

/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:
    git checkout main
    git pull --ff-only
  3. Create the branch with a kebab-case slug:
    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.

Repository
EverMind-AI/EverOS
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.