start-issue

sakuro's avatarfrom sakuro

Start working on a GitHub issue. Use when the user wants to work on an issue, start an issue, or begin implementation.

⭐2stars🔀0forks📁View on GitHub🕐Updated Jan 3, 2026

When & Why to Use This Skill

The 'start-issue' skill streamlines the initial phase of the software development lifecycle by automating the transition from GitHub issue tracking to local environment setup. It enhances developer productivity by enforcing standardized Git branching conventions, verifying repository states, and generating structured implementation roadmaps directly from issue metadata, ensuring a clean and organized start for every coding task.

Use Cases

  • Automated Branch Management: Automatically create local Git branches with standardized prefixes (feature/, fix/, refactor/) and kebab-case naming derived from GitHub issue titles and labels.
  • Workflow Standardization: Ensure developers always start from a clean, up-to-date main branch state before beginning new work, reducing merge conflicts and environment drift.
  • Task Contextualization: Quickly retrieve issue details and labels via the GitHub CLI to generate a structured implementation plan, including key file identification and step-by-step task breakdown.
  • Seamless Issue-to-Code Transition: Reduce context switching by allowing developers to initialize their workspace and understand task requirements without leaving the terminal or agent interface.
namestart-issue
descriptionStart working on a GitHub issue. Use when the user wants to work on an issue, start an issue, or begin implementation.
allowed-tools[Bash, Read, Grep]

Start Issue Skill

Assists with starting work on a GitHub issue.

IMPORTANT: When using this skill, announce to the user: "Using start-issue skill to begin work on an issue."

Workflow

1. View Issue Details

# View issue content
gh issue view [ISSUE_NUMBER]

# Check labels
gh issue view [ISSUE_NUMBER] --json labels -q '.labels[].name'

2. Verify Clean State

# Ensure on main branch with clean state
git checkout main
git pull
git status

3. Create Branch

Determine prefix based on labels:

Label Prefix
enhancement feature/
bug fix/
refactor refactor/
other chore/

Branch naming: prefix/issue-title-in-kebab-case

# Example
git checkout -b feature/implement-list-format

Branch naming rules:

  • Use kebab-case (lowercase with hyphens)
  • Keep it concise but descriptive
  • Derived from issue title
  • Examples:
    • feature/implement-list-format
    • fix/memory-leak-in-cache
    • chore/update-dependencies

4. Implementation Guide

After creating the branch:

  1. Summarize the issue - Provide a brief overview of what needs to be implemented
  2. Identify key files - If the issue specifies files to modify, list them
  3. Outline implementation steps - Break down the task into actionable steps
  4. Note test requirements - Highlight any testing needs

5. Next Steps

After implementation is complete, guide the user to:

  1. Commit changes - Use commit skill
  2. Create PR - Use create-pr skill
  3. Merge PR - Use merge-pr skill (after CI passes)

Example Workflow

# 1. View issue
gh issue view 42

# 2. Check labels
gh issue view 42 --json labels -q '.labels[].name'
# Output: enhancement

# 3. Ensure clean state
git checkout main
git pull

# 4. Create branch (prefix based on label)
git checkout -b feature/add-dark-mode

# 5. Begin implementation...

Key Rules

  • Always start from main branch with latest changes
  • Use kebab-case for branch names
  • Derive branch name from issue title - keep it concise
  • Check labels to determine appropriate prefix
  • Never include AI attribution in any output