issue-executor

Generates implementation plans for GitHub issues and creates feature branches using the Gemini CLI.

Updated Jul 13, 2024
One-click install
npx skills add https://github.com/Reading-Advantage-Thailand/codecamp-advantage --skill issue-executor-reading-advantage-thailand
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-executor
Source: https://github.com/Reading-Advantage-Thailand/codecamp-advantage/tree/main/.claude/skills/issue-executor
Command: npx skills add https://github.com/Reading-Advantage-Thailand/codecamp-advantage --skill issue-executor-reading-advantage-thailand

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Starting work on a GitHub issue often requires manually gathering issue details, spec files, and past learnings before writing any code. This Skill automates that setup by synthesizing all relevant context into a step-by-step implementation plan and creating an isolated feature branch. ## Core Features & Use Cases - Context Synthesis: Fetches issue details, referenced spec files from docs/specs or docs/changes, and the project RETROSPECTIVE.md, then uses the Gemini CLI to produce an actionable implementation plan. - Automated Branch Creation: Generates a conventional branch name (e.g., feat/45-restructure-doc-indexer) and checks it out after validating a clean git state on main. - Workflow Guidance: The references/work-on-issue.md file documents a full 15-step workflow covering issue prioritization, dependency checks, spec validation, and TODO.md/sprint file updates. - Use Case: A developer starting a sprint task runs the skill with an issue number, receives a Gemini-generated plan grounded in specs and retrospective learnings, and lands on a ready-to-code feature branch. ## Quick Start Ask the assistant to start work on issue number 45 to generate an implementation plan and create a feature branch.

Frequently Asked Questions about issue-executor

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

FAQPage Schema
How do I start work on a GitHub issue with an implementation plan?▼

Run the work-on-issue.sh script with the issue number, for example bash scripts/work-on-issue.sh 45. It fetches the issue, gathers referenced specs and the retrospective, generates a plan via the Gemini CLI, and creates a feature branch.

What tools are required to generate an issue implementation plan?▼

You need the gh CLI authenticated to GitHub, jq for JSON parsing, and the Gemini CLI installed and authenticated. The script validates jq and a clean git state before proceeding.

Why does the script fail with a working directory not clean error?▼

The script requires no uncommitted changes and that you are on the main branch. Commit, stash, or discard your changes and switch back to main before re-running it.

How are spec files included in the generated plan?▼

The script extracts markdown file paths under docs/specs/ or docs/changes/ mentioned in the issue body. Only specs explicitly referenced in the issue are included, so ensure the issue body lists full file paths.

What naming convention does the feature branch follow?▼

Branches follow the pattern feat/ISSUE_NUMBER-kebab-case-title, derived from the issue title lowercased with non-alphanumeric characters replaced by hyphens.