gh-issue-fix-flow
Skill430 starsChanged 6 months agoMITView on GitHub
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.
- Commits and pushes
3 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Vvlladd/iOSskillsCollectionedited, first seen Oct 13, 2026
- Samueladewole/claude-skillsword for word, first seen Oct 13, 2026
- ParkerRex/Skillsword for word, first seen Feb 27, 2026
Other versions3 projects use a version of this.
Word for word · 2
- ParkerRex/Skills★ 2100% same
- Samueladewole/claude-skills★ 0100% same
Edited · 1
- Vvlladd/iOSskillsCollection★ 193% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- macos/AGENTS.mdAGENTS.md
- sandbox-vm/AGENTS.mdAGENTS.md
- web/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- macos/CLAUDE.mdCLAUDE.md
- sandbox-vm/CLAUDE.mdCLAUDE.md
- app-store-changelogSkill
- bridge-agent-log-analyzerSkill
- githubSkill
- react-component-performanceSkill
- swift-concurrency-expertSkill
- swift-concurrencySkill
- swift-testing-expertSkill
- swiftui-expert-skillSkill
- swiftui-performance-auditSkill
- swiftui-ui-patternsSkill
- swiftui-view-refactorSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 6 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Use gh issue view <id> --repo <owner/repo> --comments to get the full issue context.
- Very specific: line 17
If the repo is unclear, run gh repo view --json nameWithOwner to confirm.
- Very specific: line 22
Use rg -n to locate likely files and entry points.
- Very specific: line 23
Read the relevant code paths with sed -n or rg -n context.
- Distinctive: line 24
Follow repo-specific conventions (AGENTS/CLAUDE instructions).
- Distinctive: line 29
Keep changes aligned with existing architecture and style.
- Distinctive: line 30
Add tests when behavior changes and test coverage is practical.
- Distinctive: line 34
Use XcodeBuildMCP for required builds/tests:
- Distinctive: line 38
If macOS tests fail due to deployment target mismatches, run the equivalent iOS simulator tests.
- Distinctive: line 43
Check for unrelated changes with git status --short.
- Very specific: line 45
Commit with a closing message: Fix … (closes #<issue>).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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> --commentsto get the full issue context. - If the repo is unclear, run
gh repo view --json nameWithOwnerto confirm. - Capture reproduction steps, expected behavior, and any maintainer notes.
2) Locate the code path
- Use
rg -nto locate likely files and entry points. - Read the relevant code paths with
sed -norrg -ncontext. - 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_macosormcp__XcodeBuildMCP__build_sim. - Tests: prefer targeted schemes (e.g.,
mcp__XcodeBuildMCP__test_sim).
- Set defaults once:
- 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.