# Create Git Workflow Branches

Manual branch naming can slow specification and implementation workflows. This skill guides Claude, Codex, or Claude Code to create consistent spec and impl branches.

## Install

```bash
npx skillstore add clionegohan/branch
```

## Metadata

- Status: approved
- Slug: clionegohan-branch
- Skillstore revision: r1
- Version status: missing
- Tree hash: 874c370a65f5ed900cba97eaf06d03e5df53faeca2aad462b86788d8d8430e4c
- Author: Clionegohan
- GitHub username: Clionegohan
- License: MIT
- Repository: https://github.com/Clionegohan/YoRuH-Resonance-Archive-C4-Sync-/tree/main/atdd-sdd/.claude/skills/branch
- Ref: 02f077c174c5335e2f5d02ca15e77b70d9543e58
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 70
- Public page: https://skillstore.pages.dev/skills/clionegohan-branch
- Manifest: https://skillstore.pages.dev/api/skills/clionegohan-branch/manifest

## Capabilities

- Creates branch names using spec or impl prefixes and action IDs.
- Supports optional short descriptions when forming branch names.
- Prompts for confirmation before branch creation.
- Shows the base branch and current branch after completion.
- Provides handling options for existing branches and uncommitted changes.

## Use Cases

- Start a specification branch: Create a spec branch before drafting requirements or design notes.
- Open an implementation branch: Create an impl branch before coding an approved action item.
- Standardize branch naming: Keep team branches aligned with action IDs and short descriptions.

## Prompt Templates

### Create a spec branch

```
Use the branch skill to create a spec branch for action 001-01-01 with description user-auth. Ask before running Git commands.
```

### Create an implementation branch

```
Create an impl branch for action 001-01-01 using the current repository. Confirm the base branch and branch name first.
```

### Handle an existing branch

```
Prepare a spec branch for action 002-02-03. If it already exists, show safe options before switching or creating another branch.
```

### Run a guarded branch workflow

```
Create an impl branch for action 003-04-05 payment-retry. Validate the branch name, check local changes, and ask before each Git action.
```

## Limitations

- Requires a Git repository and local command access.
- Does not define a script or automated validation logic.
- Does not manage remote branches after local creation.
- Depends on another workflow to provide accurate action IDs.

## Best Practices

- Confirm the base branch and branch name before creating anything.
- Use short descriptions with letters, numbers, and hyphens.
- Resolve uncommitted changes before switching branches.

## Anti Patterns

- Creating branches without user confirmation.
- Using long descriptions or unsupported characters in branch names.
- Discarding local changes just to make branch creation easier.

## Security Audit

- Audited at: 2026-07-05T06:21:19.172\+00:00
- Summary: Most static findings are false positives caused by Markdown backticks, code fences, and inline examples. The remaining concern is semantic: the documented Git checkout command uses a branch-name placeholder that should be validated before any shell execution.

## Stats

- Views: 190
- Downloads: 11
- Favorites: 0
- Popularity score: 0