gh-issue-fix-flow
Fix GitHub Issues With a Guided Flow
GitHub issue fixes can lose context across triage, edits, tests, and release steps. This skill gives Claude, Codex, and Claude Code a repeatable workflow for issue resolution.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "gh-issue-fix-flow" from https://skillstore.io/skills/dimillian-gh-issue-fix-flow.md and its manifest at https://skillstore.io/api/skills/dimillian-gh-issue-fix-flow/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "gh-issue-fix-flow". Fix issue 118 about a failing macOS build.
Expected outcome:
Inspected issue 118, corrected the build setting, ran the macOS build, committed the fix, and pushed the branch.
Using "gh-issue-fix-flow". Resolve issue 42 and include test results.
Expected outcome:
Updated the affected code path, added a focused test, ran simulator validation, and reported one unrelated warning.
Using "gh-issue-fix-flow". Investigate issue 77 before making changes.
Expected outcome:
Read the issue comments, identified the likely module, found missing reproduction detail, and reported the blocker before editing.
Security Audit
SafeAll ten static findings are false positives caused by Markdown inline code backticks in SKILL.md, not Ruby or shell backtick execution. The skill does guide agents to run gh, rg, XcodeBuildMCP, and git commands for user-authorized repository work. No prompt injection, hidden exfiltration, or malicious intent was found.
Risk Factors
⚙️ External commands (10)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/dimillian-gh-issue-fix-flow/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/dimillian-gh-issue-fix-flow?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/dimillian-gh-issue-fix-flow?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dimillian-gh-issue-fix-flow/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/dimillian-gh-issue-fix-flow.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Dimillian. (2026). gh-issue-fix-flow security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dimillian-gh-issue-fix-flow/audits/8BibTeX citation
@techreport{dimillian-dimillian-gh-issue-fix-flow-2026,
author = {Dimillian},
title = {gh-issue-fix-flow security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/dimillian-gh-issue-fix-flow/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "gh-issue-fix-flow security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "Dimillian"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/dimillian-gh-issue-fix-flow/audits/8"
identifiers:
- type: other
value: "skillstore:dimillian-gh-issue-fix-flow:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Resolve App Bugs
Take a reported GitHub issue from context gathering through tested code changes and a closing commit.
Contribute Focused Fixes
Follow a disciplined path for reproducing an issue, editing the right files, and reporting validation results.
Standardize Fix Workflows
Give coding agents a consistent process for issue intake, testing, commit hygiene, and final reporting.
Try These Prompts
Use gh-issue-fix-flow to fix issue 123 in this repository. Inspect the issue, make the smallest correct change, test it, and report results.
Use gh-issue-fix-flow for issue 123 in owner/repo. Confirm the repository, read comments, implement the fix, run validation, and summarize changes.
Use gh-issue-fix-flow to resolve issue 123. Add or update focused tests when practical, run XcodeBuildMCP validation, and include failures if any remain.
Use gh-issue-fix-flow to resolve issue 123 in owner/repo. Keep changes minimal, run builds and tests, commit with a closing message, and push.
Best Practices
- Confirm the repository, branch, and issue number before editing.
- Keep changes small and cite validation results in the final report.
- Review git status before staging to avoid unrelated files.
Avoid
- Pushing changes when the issue scope or repository is unclear.
- Hiding failing tests or warnings in the final report.
- Staging unrelated files with the intended fix.