github-issue-solve

Automate GitHub issues into coded fixes and pull requests with ghx.

132|13|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/holon-run/holon --skill github-issue-solve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issue-solve
Source: https://github.com/holon-run/holon/tree/main/skills/github-issue-solve
Command: npx skills add https://github.com/holon-run/holon --skill github-issue-solve

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the end-to-end workflow of turning GitHub issues into coded fixes and pull requests, reducing manual handoffs and speeding up delivery.

Core Features & Use Cases

  • Analyze issue contexts (title, body, and comments) to derive requirements.
  • Implement code changes, create a feature branch, commit, push, and open or update a PR with a clear summary.
  • Support headless operation using ghx by default and gh as a fallback, with outputs written to summary and manifest artifacts for CI.

Quick Start

Initiate the workflow by providing an issue to solve; the skill will implement the solution, push a feature branch, and publish a pull request with a summary.

Frequently Asked Questions about github-issue-solve

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

FAQPage Schema
How do I automate GitHub issue fixes and pull request creation?

To automate GitHub issue fixes, this skill analyzes issue context, implements code changes, creates a feature branch, commits, pushes, and opens a pull request with a descriptive summary entirely headless.

What is the best way to turn GitHub issues into coded fixes automatically?

Turning GitHub issues into coded fixes is best handled by analyzing issue titles, bodies, and comments to derive requirements, then implementing changes and pushing a feature branch with an automated pull request.

Does this automated PR creation tool work with headless CI environments?

Yes, automated PR creation works in headless CI environments by using ghx by default with gh as a fallback, outputting summary.md and manifest.json artifacts for downstream pipeline automation.

Can I use this to update an existing pull request after pushing new commits?

Yes, you can use this to update an existing pull request; the workflow evaluates the current repository state and opens or updates a pull request with a clear descriptive summary of the implemented changes.

Do I need to manually create a feature branch before automating issue resolution?

No, you do not need to manually create a feature branch; the automation derives requirements from the issue context, implements the code changes, creates the branch, and pushes the commits directly.