skills.rest
KazusaNakagawa
KazusaNakagawaCOMMUNITY
Explore all skills by this author →
𝕏@kazusa_nakagawaGitHub

start

Create a feature branch and open a PR from a GitHub Issue number.

Updated Mar 14, 2026
Search Tags:#git#workflow#github#branch#issue#pull-request#start
One-click install
npx skills add https://github.com/KazusaNakagawa/claude_docs --skill start-kazusanakagawa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: start
Source: https://github.com/KazusaNakagawa/claude_docs/tree/main/.claude/skills/start
Command: npx skills add https://github.com/KazusaNakagawa/claude_docs --skill start-kazusanakagawa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start development from a GitHub Issue number by automating the initial setup and workflow scaffolding.

Core Features & Use Cases

  • Fetch and update the develop branch to ensure up-to-date base
  • Create a feature branch named after the issue
  • Push the branch and create a PR with a standardized format
  • Enforce English PR titles and consistent naming
  • Applicable to issue-driven workflows across small to large repos

Quick Start

Run the start command with an issue number to begin work on that GitHub issue.

Frequently Asked Questions about start

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

FAQPage Schema
How do I start development on a GitHub issue by creating a feature branch and PR?▼

To start development on a GitHub issue, this Skill automates syncing the develop branch, creating a feature branch named after the issue, and opening a standardized PR. You simply run the start command with the issue number to scaffold the entire workflow.

What is the best way to keep my feature branch updated with the develop branch before starting work?▼

The best way to keep your feature branch updated is by syncing the develop branch first. This Skill fetches and updates the develop branch automatically before creating your feature branch, ensuring your base is completely up-to-date.

Does this issue-driven workflow enforce consistent PR titles and branch naming conventions?▼

Yes, this issue-driven workflow enforces consistency by applying conventional branch-management practices. It creates issue-named feature branches and pushes standardized PR formats, including enforcing English PR titles across small to large repos.

Can I use GitHub CLI to automate pull request provisioning from an issue number?▼

Yes, you can use GitHub CLI to automate pull request provisioning. This Skill relies on Git and GitHub CLI to read issue details, push the feature branch, and open a PR with a standardized format directly from the issue number.

What do I need to set up before automating feature-branch creation from GitHub issues?▼

Before automating feature-branch creation, you need Git and GitHub CLI installed and configured. The workflow assumes an issue-driven development process organized around a develop branch to enforce consistent naming and PR scaffolding.

Related Skills

Explore More Software Engineering Skills→
1gy1gy

managing-branches

Inspect Git workspace status and create branches from a base branch.

Community
Intermediate
avvaleavvale

commit-pr

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

Official
Advanced
luongnv89luongnv89
104

devops-pipeline

Automate pre-commit hooks and GitHub Actions for code quality.

Community
Advanced
buddypiabuddypia

create-pr

Automate Git pull request creation from feature branches to develop.

Community
Advanced