gh-issue-fix-flow

Automate GitHub issue resolution from inspection through build, test, and push.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the entire process of addressing a GitHub issue, from initial inspection and code fixing to testing and final push, streamlining developer workflow.

Core Features & Use Cases

  • Issue Triage: Fetches full issue context using gh.
  • Code Navigation: Locates relevant code paths using rg.
  • Automated Builds & Tests: Executes builds and tests via XcodeBuildMCP.
  • Git Integration: Commits and pushes fixes with appropriate closing messages.
  • Use Case: When assigned a bug report on GitHub, this Skill can automatically fetch the issue details, identify the problematic code, implement a fix, run the necessary tests, and commit the changes.

Quick Start

Use the gh-issue-fix-flow skill to fix issue number 123 in the current repository.

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 resolution from start to finish?

You can automate GitHub issue resolution by fetching context with `gh`, locating code with `rg`, implementing fixes, running tests via `XcodeBuildMCP`, and pushing commits with closing messages to fully streamline bug fixing.

What is the process for linking a code fix to a specific GitHub issue?

Linking a code fix to a GitHub issue requires committing changes with a closing message referencing the issue number. The automated workflow fetches issue details, applies fixes, validates tests, and pushes the git commit with the appropriate closing syntax.

Can I use XcodeBuildMCP to validate code changes for a GitHub bug fix?

Yes, XcodeBuildMCP executes automated builds and tests to validate code changes during the GitHub bug fixing workflow. It ensures the local code modifications pass necessary tests before committing and pushing the fix to the repository.

Does this automated git workflow require manual code navigation to find bugs?

No, the automated git workflow uses `rg` for code navigation to locate relevant code paths after fetching issue context with `gh`. It identifies problematic code automatically based on the GitHub issue details before applying fixes.

What are the limitations of automating issue tracking and bug fixing workflows?

Limitations include dependency on `gh` for issue context, `rg` for code search, and `XcodeBuildMCP` for validation, meaning the workflow is tailored for environments supporting these tools and may require manual intervention for highly complex or ambiguous issue descriptions.