skills.rest
Sn005
Sn005COMMUNITY
Explore all skills by this author →
WebsiteGitHub

branch

Create deterministic Git branches with spec/ or impl/ prefixes.

1|Updated Dec 31, 2025
Search Tags:#automation#git#workflow#spec#branch#impl
One-click install
npx skills add https://github.com/Sn005/recommend-scp --skill branch-sn005
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch
Source: https://github.com/Sn005/recommend-scp/tree/main/.claude/skills/branch
Command: npx skills add https://github.com/Sn005/recommend-scp --skill branch-sn005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates deterministic Git branches for specification or implementation work, ensuring consistent naming and integration with the SDD workflow.

Core Features & Use Cases

  • Automatic branch naming: Generates branches using the correct prefixes (spec/ for spec work, impl/ for implementation) and action identifiers.
  • Workflow integration: Triggers from /spec for spec-phase work and from spec-workflow for implementation-phase work.
  • Guardrails: Performs duplicate checks and prompts for user confirmation before creating a branch to prevent accidental overwrites.

Quick Start

Invoke the branch command with a type (spec or impl) and an action-id to create the corresponding branch, for example: /branch spec 001-01-01

Frequently Asked Questions about branch

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

FAQPage Schema
How do I automate Git branch creation for spec and implementation workflows?▼

Automating Git branch creation for spec and impl workflows involves generating deterministic branch names with correct prefixes and action identifiers. This approach ensures consistent version control practices in AI-driven development by enforcing naming conventions.

What are the naming conventions for spec and impl branches in AI-driven development?▼

Spec and impl branches in AI-driven development use prefixed naming conventions like spec/ for specification work and impl/ for implementation phases. These deterministic branch names integrate with the SDD workflow to maintain version control consistency.

How do I prevent accidental overwrites when creating Git branches for specifications?▼

Preventing accidental overwrites when creating Git branches requires guardrails like duplicate checks and user confirmation prompts. Verifying branch existence before creation ensures existing specification or implementation branches are not accidentally overwritten.

Does the branch Skill require manual confirmation before creating a new Git branch?▼

The branch Skill requires user confirmation before creating a new Git branch. It performs duplicate checks and prompts the user to verify the action, preventing accidental overwrites and ensuring branches comply with safety conventions.

How do I create a spec branch using an action identifier?▼

To create a spec branch using an action identifier, invoke the branch command with the type and action-id, such as /branch spec 001-01-01. This generates a deterministic Git branch with the spec/ prefix for specification work.

When do I need to use the impl branch prefix instead of spec?▼

You need to use the impl branch prefix instead of spec when transitioning from the specification phase to the implementation phase. The spec/ prefix applies to specification work, while impl/ is used for triggering implementation workflows.

Related Skills

Explore More Software Engineering Skills→
MusoyanGrigorMusoyanGrigor
5

gitx

Automate Git repository management with smart commits and safe synchronization workflows.

Community
Advanced
JoeCP17JoeCP17
8

commit-push

Stage changes, create a conventional commit, and push to the remote branch.

Community
Intermediate
YoniChechikYoniChechik

create-clone

Create an isolated git clone and feature branch from a feature description.

Community
Basic
iani-kuliiani-kuli

create-branch

Create git branches with standardized names from user identity and diffs.

Community
Intermediate