skills.rest
hirokimry
hirokimryCOMMUNITY
Explore all skills by this author →
Website𝕏@hirokimryGitHub

branch

Create and check out a Git branch from a GitHub Issue URL.

1|Updated Mar 20, 2026
Search Tags:#automation#git#github#branching#worktree#issues
One-click install
npx skills add https://github.com/hirokimry/vibecorp --skill branch-hirokimry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch
Source: https://github.com/hirokimry/vibecorp/tree/main/skills/branch
Command: npx skills add https://github.com/hirokimry/vibecorp --skill branch-hirokimry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of manually naming, creating, and checking out feature branches when a GitHub Issue already defines the work.

Core Features & Use Cases

  • Turns a GitHub Issue URL into a consistent dev/{issue_number}_{summary} branch name.
  • Updates the base branch first so new work starts from the latest remote state.
  • Supports an optional worktree mode for isolated workspaces when you want parallel development.
  • Use it when you need a fast, repeatable way to start implementation work directly from an issue.

Quick Start

Ask the assistant to create a branch from the GitHub Issue URL and it will make the branch, check it out, and return the final branch name.

Frequently Asked Questions about branch

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 URL automatically?▼

To create a Git branch from a GitHub Issue URL, provide the URL to the assistant. It fetches the issue title, converts it into a dev/{issue_number}_{summary} format, refreshes the base branch, and checks out the new branch.

Does this branching workflow require GitHub CLI and jq to fetch issue metadata?▼

Yes, creating issue-based branches requires Git, GitHub CLI, and jq. These dependencies are necessary to fetch GitHub issue metadata, refresh the remote base branch state, and prevent branch-name collisions.

What is the best way to name feature branches consistently from GitHub issues?▼

The best way to name feature branches consistently from GitHub issues is using a dev/{issue_number}_{summary} naming convention. This automatically converts the issue title into a standardized branch name.

Can I use a git worktree for isolated workspaces when starting work from an issue?▼

Yes, you can use an optional git worktree mode for isolated workspaces. This supports parallel development by creating an isolated workspace directly from the GitHub issue branch.

How does this process prevent branch-name collisions when creating new feature branches?▼

It prevents branch-name collisions by checking existing branches before creating a new one. It fetches issue metadata via GitHub CLI and jq to ensure the generated dev/{issue_number}_{summary} name is unique.

Why does the workflow update the base branch before checking out a new issue branch?▼

Updating the base branch before checking out a new issue branch ensures new work starts from the latest remote state. This keeps the newly created feature branch aligned with the current repository state.

Related Skills

Explore More Software Engineering Skills→
beshkenadzebeshkenadze
3

git-worktree-workflow

Create and manage git worktrees for isolated feature branches.

Community
Intermediate
avvaleavvale

commit-pr

Commit changes, push to a feature branch, and create a GitHub Pull Request.

Official
Advanced
EmasoftEmasoft
13

amoa-github-action-integration

Automate Claude Code GitHub Actions for PR review, mention responses, and issue triage.

Community
Intermediate
mvillmowmvillmow
18

worktree-switch

List and switch between Git worktrees for parallel development.

Community
Basic