OpenParable
Skip to content
← Back to skills

New Branch

Development
new-branch

New Branch is an Agent Skill for development published in the EverMind-AI/EverOS repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Create a GitHub branch from main with the project naming convention

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/EverMind-AI/EverOS/blob/HEAD/.claude/skills/new-branch/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/new-branch, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

/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.