github-issue-runner

Process GitHub issues sequentially from ISSUE_WORKPLAN.md with branches and pull requests.

1|Updated May 14, 2026
One-click install
npx skills add https://github.com/MarcoAntolini/cursor-sync --skill github-issue-runner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issue-runner
Source: https://github.com/MarcoAntolini/cursor-sync/tree/main/cursor-skills/github-issue-runner
Command: npx skills add https://github.com/MarcoAntolini/cursor-sync --skill github-issue-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of working through GitHub issues, managing workplans, and facilitating code review and pull request creation.

Core Features & Use Cases

  • Sequential Issue Processing: Automatically process issues from a ISSUE_WORKPLAN.md file, one issue per branch or pull request.
  • Issue Tracking and Reporting: Keep track of progress and report completion or blockages for each issue.
  • Use Case: Ideal for development teams looking to automate the issue handling process, reducing manual intervention and speeding up workflows.

Quick Start

Run the 'github-issue-runner' skill to automatically process issues from the 'ISSUE_WORKPLAN.md' file.

Frequently Asked Questions about github-issue-runner

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

FAQPage Schema
How do I automate GitHub issue processing from a workplan file?

Automating GitHub issue processing involves sequentially reading issues from an `ISSUE_WORKPLAN.md` file, creating a dedicated branch for each issue, and generating pull requests. This approach reduces manual intervention and streamlines development workflows.

Do I need the gh command-line tool to automate issue tracking and pull request creation?

Yes, you need the `gh` command-line tool installed to automate issue tracking and pull request creation. The Skill relies on `gh` for GitHub API interaction and basic issue and PR manipulation across your repositories.

Can I track issue progress and report blockages automatically using GitHub workflows?

Yes, you can track issue progress and report blockages automatically. The sequential processing mechanism monitors each issue's status, reporting completion or blockages back to the workplan to keep development teams updated.

What is the best way to manage multiple GitHub issues and generate pull requests for each?

The best way to manage multiple GitHub issues is using an automated sequential processing approach that reads from an `ISSUE_WORKPLAN.md` file. It handles branching and pull request creation for each issue, speeding up code review workflows.

Does sequential issue automation support branching for individual GitHub issues?

Yes, sequential issue automation supports branching for individual GitHub issues. The processing logic creates one branch per issue defined in the workplan file, ensuring isolated development environments before initiating the pull request phase.