code-branch

Create a dedicated git branch or worktree for isolated coding tasks.

7|1|Updated Mar 19, 2026

Search Tags:#git #isolation #branching #worktree #version-control #coding-workflow

Ready to run

npx skills add https://github.com/Shiien/Self-Evolved-Research-Framework --skill code-branch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-branch
Source: https://github.com/Shiien/Self-Evolved-Research-Framework/tree/main/skills/code-branch
Command: npx skills add https://github.com/Shiien/Self-Evolved-Research-Framework --skill code-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you start coding tasks in an isolated workspace by creating a dedicated git branch or a dedicated worktree to keep large changes separate from the main line, while preserving the current branch for smaller edits.

Core Features & Use Cases

Named branching with prefixes exp/, feat/, or fix/ to organize work.
Creation and switching to a new worktree for long-running tasks.
Clear reporting of the new context to downstream skills and planning.

Quick Start

Start by asking to isolate this task or create a worktree for a medium-scale implementation.

Frequently Asked Questions about code-branch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I isolate coding work in a separate git branch without disturbing my current branch?▼

To isolate coding work without disturbing your current branch, this skill creates a dedicated git branch using predefined prefixes like feat/, fix/, or exp/ before you start non-trivial development. It enforces naming conventions and communicates the new context to downstream skills.

When should I use a git worktree instead of just creating a new branch?▼

Use a git worktree instead of a standard branch for long-running tasks or large refactors where you need an isolated physical directory. A standard branch is sufficient for smaller edits, but worktrees provide deeper isolation without disrupting your current working directory.

What branch naming conventions are enforced for feature development and experiments?▼

Branch naming conventions enforced for feature development and experiments require specific prefixes: feat/ for features, fix/ for refactors, and exp/ for experiments. These rules are loaded from shared git-conventions to maintain consistent version-control organization.

Can I use this branching workflow for large checklist implementations and refactors?▼

Yes, you can use this workflow for large checklist implementations and refactors. It safely isolates these non-trivial coding tasks by setting up a dedicated branch or worktree first, ensuring your main version-control line remains undisturbed until the work is ready.