skills.rest
shoji9x9
shoji9x9COMMUNITY
Explore all skills by this author →
𝕏@shoji9x9GitHub

issue-start

Standardizes GitHub Issue-driven workflows from branch creation through pull request submission.

Updated Jul 24, 2026
Search Tags:#git#workflow#pull request#github#gh cli#branch#issue
One-click install
npx skills add https://github.com/shoji9x9/portfolio --skill issue-start-shoji9x9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-start
Source: https://github.com/shoji9x9/portfolio/tree/main/.agents/skills/issue-start
Command: npx skills add https://github.com/shoji9x9/portfolio --skill issue-start-shoji9x9

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Starting work from a GitHub Issue involves repetitive manual steps: verifying the repository matches the Issue, naming and creating a feature branch, checking for duplicate branches, and following repo-specific commit conventions. This Skill standardizes that entire flow using the GitHub CLI so nothing is skipped or done inconsistently. ## Core Features & Use Cases - Issue-to-branch automation: Extracts owner/repo/issue number from a URL or number, verifies repository match, reads the Issue body and comments, and creates a feature/<number>-<description> branch via gh issue develop. - Staged execution modes: Supports --plan (investigate and draft a detailed plan only), --commit (implement and commit in logical units), and --pr (implement, commit, push, and open a pull request), with no commits unless explicitly delegated. - Convention resolution: Resolves branch naming, base branch, and commit message rules per repository via a config file, standard docs like AGENTS.md, or user confirmation, with safeguards against duplicate branches, --amend, and force pushes. - Use Case: You receive Issue #220 asking for a new settings page. Run the Skill with the Issue number and --pr to create the branch, implement the change, commit per repo conventions, push, and open a linked pull request. ## Quick Start Ask the AI to start working on a GitHub Issue by saying "start work on issue 220 with --pr" or by pasting the Issue URL.

Frequently Asked Questions about issue-start

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

FAQPage Schema
How do I create a feature branch from a GitHub Issue?▼

Pass the Issue URL or number to the Skill, which extracts owner, repo, and issue number, verifies the repository matches, then runs gh issue develop with a feature/<number>-<description> branch name based on the resolved base branch.

How to go from GitHub Issue to pull request automatically?▼

Use the --pr mode: after branch creation it implements the change, stages only related files, commits in logical units per repo conventions, pushes the branch, and opens a pull request linking the Issue with a change summary.

Does this work with repositories that use develop instead of main?▼

Yes. The base branch is resolved from repository conventions via a config file, AGENTS.md, CLAUDE.md, or CONTRIBUTING.md rather than being hardcoded to main. If no convention is found, it asks the user before proceeding.

What happens if a branch for the same issue already exists?▼

The Skill checks local and remote branches matching feature/<number>-* before creating anything. If exactly one matching branch exists with clear intent, it checks it out and continues; if multiple or ambiguous, it asks the user.

Why does gh issue view --comments miss the issue body in scripts?▼

In non-TTY contexts such as agent or piped execution, gh issue view --comments outputs only comments, not the body. The Skill works around this by using gh issue view --json title,body,comments to fetch everything in one call.

What are the limitations of the issue-start workflow?▼

It requires gh and git in a bash-compatible shell (WSL or Git Bash on Windows) and never performs amend commits or force pushes. It also stops and asks the user when the Issue belongs to a different repository or requirements are ambiguous.

Related Skills

Explore More Software Engineering Skills→
PelekePeleke

issue

Draft structured GitHub issues with titles, descriptions, and acceptance criteria.

Community
Intermediate
JeqqeJeqqe

integrate

Merge CI-green issue branches into one release pull request.

Community
Advanced
johinsDevjohinsDev

tooling

Enforce linting, formatting, typechecking, and commit-message rules via lefthook and commitlint.

Community
Intermediate
JansenAnalyticsJansenAnalytics
5

github-workflow

Automate Git and GitHub tasks including cloning, branching, committing, pushing, PRs, issues, and CI status.

Community
Intermediate