skills.rest
MAdrid1011
MAdrid1011COMMUNITY
Explore all skills by this author →
GitHub

fork-dev-branch

Create a local GitHub issue branch with standardized naming and switch to it.

1|2|Updated Sep 17, 2025
Search Tags:#automation#git#workflow#github#branch#issue#naming
One-click install
npx skills add https://github.com/MAdrid1011/Zircon-VLIW --skill fork-dev-branch-madrid1011
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fork-dev-branch
Source: https://github.com/MAdrid1011/Zircon-VLIW/tree/main/.claude/skills/fork-dev-branch
Command: npx skills add https://github.com/MAdrid1011/Zircon-VLIW --skill fork-dev-branch-madrid1011

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of development branches that are consistently named for GitHub issues, reducing manual setup time and naming mistakes.

Core Features & Use Cases

  • Extracts the issue number from context or user input and validates its existence.
  • Generates a branch title in the format issue-<number>-<brief-title> (lowercase, hyphens, 3-5 words).
  • Creates and switches to the new local branch, ready for implementation work.
  • Handles errors for missing, invalid, or closed issues with clear guidance.

Quick Start

Create a new branch for the identified issue using the standard naming format and switch to it.

Frequently Asked Questions about fork-dev-branch

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

FAQPage Schema
How do I create a standardized git branch from a GitHub issue?▼

To create a standardized git branch from a GitHub issue, the Skill extracts the issue number and title, validates its existence, and generates a local branch named issue-<number>-<brief-title> while switching to it automatically.

What naming convention does this workflow enforce for GitHub issue branches?▼

The naming convention enforced for GitHub issue branches requires lowercase letters and hyphens, formatting the branch as issue-<number>-<brief-title> with a concise three to five words derived from the original issue title.

What happens if I try to create a branch for a closed or invalid GitHub issue?▼

If you attempt to create a branch for a closed or invalid GitHub issue, the automation validates the issue status and reports actionable errors, ensuring branches are only generated for valid, open issues.

How do I automate GitHub branch creation to avoid manual naming mistakes?▼

You automate GitHub branch creation to avoid manual naming mistakes by using a workflow that extracts the issue context, applies strict lowercase and hyphen formatting rules, and creates the local branch automatically.

Does this automation require manual input of the GitHub issue number?▼

This automation does not strictly require manual input of the GitHub issue number; it extracts the issue number directly from the current context, though user input is supported to identify the target issue.

Related Skills

Explore More Software Engineering Skills→
alpoxdevalpoxdev
3

git-issue

Automates GitHub issue creation and links local branches to them.

Community
Advanced
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
cameronraysmithcameronraysmith
14

preferences-git-version-control

Enforce Git atomic commits, branch naming, and GitHub PR/Issue protocols.

Community
Advanced
e-stpierree-stpierre
1

af-git-branch

Create and checkout git branches with standardized kebab-case naming.

Community
Intermediate