Gh issue fix flow

Skill aiskillstore/marketplace/skills/dimillian/gh-issue-fix-flow

Security-audited skills for Claude, Codex & Claude Code. One-click install, quality verified.

Install

npx -y skills add aiskillstore/marketplace --skill gh-issue-fix-flow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

End-to-end GitHub issue fix workflow using gh, local code changes, builds/tests, and git push. Use when asked to take an issue number, inspect the issue via gh, implement a fix, run XcodeBuildMCP builds/tests, commit with a closing message, and push.

SKILL.md

1.9 KB, as published. Nobody here has run it

Gh Issue Fix Flow

Overview

Resolve a GitHub issue from intake through fix, validation, and push using gh, local edits, XcodeBuildMCP, and git.

Workflow

1) Intake and issue context

Use gh issue view <id> --repo <owner/repo> --comments to get the full issue context.
If the repo is unclear, run gh repo view --json nameWithOwner to confirm.
Capture reproduction steps, expected behavior, and any maintainer notes.

2) Locate the code path

Use rg -n to locate likely files and entry points.
Read the relevant code paths with sed -n or rg -n context.
Follow repo-specific conventions (AGENTS/CLAUDE instructions).

3) Implement the fix

Edit the minimal set of files.
Keep changes aligned with existing architecture and style.
Add tests when behavior changes and test coverage is practical.

4) Build and test

Use XcodeBuildMCP for required builds/tests:
- Set defaults once: mcp__XcodeBuildMCP__session-set-defaults.
- Build: mcp__XcodeBuildMCP__build_macos or mcp__XcodeBuildMCP__build_sim.
- Tests: prefer targeted schemes (e.g., mcp__XcodeBuildMCP__test_sim).
If macOS tests fail due to deployment target mismatches, run the equivalent iOS simulator tests.
Report warnings or failures; do not hide them.

5) Commit and push

Check for unrelated changes with git status --short.
Stage only the fix (exclude unrelated files).
Commit with a closing message: Fix … (closes #<issue>).
Push with git push.

6) Report back

Summarize what changed and where.
Provide test results (including failures).
Note any follow-ups or blocked items.