fork-dev-branch

Name: fork-dev-branch
Availability: InStock
Author: fengqiyu0317

Create a GitHub development branch named issue-<number>-<brief-title> from an issue.

1|Updated Dec 17, 2025

Search Tags:#automation #git #github #branching #issue-tracking #branch-naming

Ready to run

npx skills add https://github.com/fengqiyu0317/assassyn --skill fork-dev-branch-fengqiyu0317

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fork-dev-branch
Source: https://github.com/fengqiyu0317/assassyn/tree/main/assassyn-master/.claude/skills/fork-dev-branch
Command: npx skills add https://github.com/fengqiyu0317/assassyn --skill fork-dev-branch-fengqiyu0317

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill automates the creation of consistently named development branches for GitHub issues, reducing manual naming errors and improving traceability across the team's workflow.

Core Features & Use Cases

Standardized branch naming: Generates issue-based branch names following the pattern issue-<number>-<brief-title>.
Issue extraction and validation: Detects the issue number from context or user input and confirms the issue exists in the repository.
Branch creation and confirmation: Creates and switches to the new branch, then returns a clear success message.

Quick Start

Provide the GitHub issue number and let the AI create a development branch named in the issue-<number>-<brief-title> format.

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 development branch from a GitHub issue automatically?▼

Creating a standardized branch from a GitHub issue requires extracting the issue number, converting the title to a hyphenated name, and generating a branch named issue-<number>-<brief-title>. This approach reduces manual naming errors and improves workflow traceability.

What is the standard naming convention for Git branches based on issue numbers?▼

The standard naming convention for Git branches based on issues is issue-<number>-<brief-title>. This format extracts the issue number and converts the title into a concise hyphenated branch name to maintain consistency across repository projects.

Do I need to manually enter the issue title when creating a branch from an issue?▼

No, you do not need to manually enter the issue title when creating a branch. The process extracts the issue number from context or input, validates the issue exists in the repository, and automatically converts the title to a concise hyphenated branch name.

Can I automate branch naming across multiple GitHub repository projects?▼

Yes, you can automate branch naming across multiple GitHub repository projects by applying a standard naming convention. It extracts the issue number, generates a consistent issue-<number>-<brief-title> format, and creates the branch to ensure uniform traceability.

What happens if an invalid GitHub issue number is provided for branch creation?▼

When an invalid GitHub issue number is provided for branch creation, the process performs issue validation before proceeding. It confirms the issue exists in the repository to prevent errors and stops the branch generation if the issue is not found.