gh-issue-fix-flow

Automate GitHub issue resolution from intake through fix, build, and push.

3|2|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/dagba/ios-mcp --skill gh-issue-fix-flow-dagba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-issue-fix-flow
Source: https://github.com/dagba/ios-mcp/tree/main/skills/gh-issue-fix-flow
Command: npx skills add https://github.com/dagba/ios-mcp --skill gh-issue-fix-flow-dagba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates an end-to-end GitHub issue resolution workflow, enabling automated intake, context gathering, code changes, builds, and pushes with minimal manual intervention.

Core Features & Use Cases

  • Intake & Context: Retrieve issue context, reproduce steps, and determine scope using gh.
  • Codepath Discovery & Fixes: Locate likely code paths, apply minimal, targeted fixes that align with project conventions.
  • Build, Test & Validate: Run builds and tests via XcodeBuildMCP to verify fixes across targeted schemes.
  • Commit, Close & Push: Commit with a closing message (closes #<issue>) and push changes to the repository.
  • Traceability: Provide an audit trail of changes and test results for maintainers.

Quick Start

Trigger the flow by providing the issue number and repository. Example: gh issue view 123 --repo owner/repo --comments to gather context, then proceed to locate, fix, build, test, commit with a closing message, and push.

Frequently Asked Questions about gh-issue-fix-flow

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

FAQPage Schema
How do I automate GitHub issue fixes end-to-end including build and push?

Automating GitHub issue fixes involves retrieving context with gh, locating code paths, applying minimal changes, running builds via XcodeBuildMCP, and pushing commits with a closing message. This end-to-end workflow minimizes manual intervention from intake through verification.

Can I use XcodeBuildMCP to verify code changes for GitHub issues?

Yes, XcodeBuildMCP is used to run builds and tests to verify fixes across targeted schemes. It validates code changes locally before committing and pushing the resolution back to the GitHub repository.

What is the best way to commit and close a GitHub issue automatically?

The best way to close a GitHub issue automatically is to commit the fix with a closing message like "closes #<issue>" and push the changes. This links the commit to the issue, closing it upon merge.

Do I need gh and XcodeBuildMCP to automate issue triage and patching?

Yes, you need gh to parse issue context and determine scope, and XcodeBuildMCP to run builds and tests. Both tools are required to orchestrate the end-to-end resolution workflow from intake to push.

How does an automated GitHub issue resolution workflow handle codepath discovery?

The workflow parses issue context retrieved via gh to locate likely code paths. It then applies minimal, targeted fixes that align with existing project conventions before validating the changes through builds.

What are the limitations of using gh for automated GitHub issue resolution?

Using gh for automated issue resolution requires a local environment with XcodeBuildMCP for validation. It is limited to GitHub-hosted projects and relies on local edits to apply minimal targeted fixes before building and pushing.