start-issue

Creates Git branches from GitHub issues based on label-derived branch types.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Hand-Tomi/text_bridge --skill start-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-issue
Source: https://github.com/Hand-Tomi/text_bridge/tree/main/.claude/skills/start-issue
Command: npx skills add https://github.com/Hand-Tomi/text_bridge --skill start-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of creating a new Git branch based on a GitHub issue, streamlining the development workflow.

Core Features & Use Cases

  • Issue-driven Branching: Automatically creates branches named according to project conventions (e.g., feature/123-issue-title).
  • Branch Type Mapping: Infers the branch type (feature, fix, hotfix, chore) from issue labels.
  • Git Flow Adherence: Follows specified Git flow rules for branch creation and naming.
  • Use Case: When a new bug is reported on GitHub, this Skill can create a fix/ branch automatically, ready for development.

Quick Start

Use the start-issue skill to create a branch for issue number 5.

Frequently Asked Questions about start-issue

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

FAQPage Schema
How do I create a Git branch from a GitHub issue automatically?

To create a Git branch from a GitHub issue, this Skill parses issue details and generates a branch name based on project conventions. It automatically creates and checks out the branch, streamlining your development workflow.

How does branch type mapping work with GitHub issue labels?

Branch type mapping infers the Git branch type by reading GitHub issue labels. It categorizes branches into types like feature, fix, hotfix, or chore based on the specific labels applied to the issue.

Can I use this to follow git-flow branching conventions?

Yes, you can use this to follow git-flow conventions. The Skill adheres to specified Git flow rules for branch creation and naming, ensuring your issue-driven branches align with standard workflows.

What is the best way to name feature branches from issue tracking numbers?

The best way to name feature branches from issue tracking numbers is using project conventions like feature/123-issue-title. This Skill parses the GitHub issue title and number to generate standardized branch names.

Do I need any specific dependencies to automate branch creation from issues?

No specific dependencies are required to automate branch creation from issues. The Skill operates independently using scripts and references to parse GitHub issue details and execute Git commands.