issue-to-branch-start

Create or reuse a linked branch with deterministic naming from a planning issue.

Updated Aug 23, 2026

Search Tags:#git #workflow #implementation #deterministic #branch #issue #start

Ready to run

npx skills add https://github.com/ai212983/gh-csi --skill issue-to-branch-start

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-to-branch-start
Source: https://github.com/ai212983/gh-csi/tree/main/skills/issue-to-branch-start
Command: npx skills add https://github.com/ai212983/gh-csi --skill issue-to-branch-start

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start implementation from the finalized planning issue by creating or reusing a linked branch with deterministic naming.

Core Features & Use Cases

Ensures you begin coding from the canonical issue context.
Creates or reuses a linked branch with a deterministic, concise name.
Validates a clean working tree and reports whether the branch was created or reused.

Quick Start

Run the issue-to-branch-start workflow to begin implementation from the current planning issue.

Frequently Asked Questions about issue-to-branch-start

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

FAQPage Schema

How do I create a git branch from an issue with a deterministic naming convention?▼

To create a git branch from an issue with deterministic naming, start implementation from the finalized planning issue. This workflow creates or reuses a linked branch with a concise, predictable name and reports its creation or reuse status.

What is the best way to link a git workflow branch to a planning issue?▼

Linking a git workflow branch to a planning issue requires a finalized plan or a canonical plan marker. The workflow enforces deterministic branch naming, connects the branch to the source issue, and ensures you begin coding from the canonical issue context.

Do I need a clean working tree before starting implementation from a new branch?▼

Yes, you need a clean working tree before starting implementation from a new branch. The workflow validates the working tree state before creating or reusing the linked branch, ensuring a predictable base for your deterministic branch name.

What happens if a branch linked to an issue already exists when starting implementation?▼

If a branch linked to an issue already exists when starting implementation, the workflow reuses the existing branch. It reports the reuse status and the base branch, preventing duplicate branches and maintaining deterministic naming across your git workflow.

Can I start coding from an issue without a finalized planning issue or canonical plan marker?▼

No, you cannot start implementation without a finalized planning issue or canonical plan marker. This workflow is applicable only when a plan exists, ensuring the branch context is fully established before creating the deterministic branch name.