issue-executor

Create a feature branch and implementation plan for a GitHub issue.

11|3|Updated Oct 21, 2025
One-click install
npx skills add https://github.com/bodangren/git-workflow --skill issue-executor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-executor
Source: https://github.com/bodangren/git-workflow/tree/main/.claude/skills/issue-executor
Command: npx skills add https://github.com/bodangren/git-workflow --skill issue-executor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, gemini, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of starting work on a GitHub issue by automatically gathering all necessary context and preparing your development environment.

Core Features & Use Cases

  • Context Synthesis: Consolidates issue details, specifications, and retrospective notes into a coherent implementation plan.
  • Automated Branching: Creates a dedicated feature branch for isolated development.
  • Use Case: When you're assigned a new issue like "Implement user authentication," this Skill will read the issue description, find related spec files, review past project learnings, and generate a step-by-step plan before creating a branch named feat/123-implement-user-authentication.

Quick Start

Use the issue executor skill to start work on issue number 45.

Frequently Asked Questions about issue-executor

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

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

To automatically create a feature branch from a GitHub issue, this Skill fetches issue details and generates a conventional branch name like `feat/123-issue-title` to isolate your development work.

How do I generate an implementation plan from a GitHub issue description?

You can generate an implementation plan from a GitHub issue description by synthesizing the issue context, identifying relevant specification files, and using the Gemini CLI to create a step-by-step development plan.

Do I need the gh CLI and jq installed to automate issue tracking and branching?

Yes, you need the `gh` CLI and `jq` installed to automate issue tracking and branching, as these dependencies are required to fetch GitHub issue details and process the JSON context for development workflow automation.

What is the best way to synthesize project context before starting development on a new issue?

The best way to synthesize project context before starting development is to consolidate issue details, specification files, and retrospective notes into a coherent implementation plan using an AI assistant.

Can I use this development workflow automation for any GitHub repository?

You can use this development workflow automation for any GitHub repository where you have access to fetch issue details and create branches using the `gh` CLI and Gemini CLI.

Why does the automated feature branch creation use a kebab-case title format?

Automated feature branch creation uses a kebab-case title format to ensure branch names are conventional, readable, and safely parsed by Git, preventing spacing issues in your development workflow.