# 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

```bash
npx skillstore add dimillian/gh-issue-fix-flow
```

## Metadata

- Status: approved
- Slug: dimillian-gh-issue-fix-flow
- Skillstore revision: r1
- Version status: missing
- Tree hash: adcaf9c670f8769e682e8edc63c28bd05728591a8cbaebe96ea3a0dbe560c953
- Author: Dimillian
- GitHub username: Dimillian
- License: MIT
- Repository: https://github.com/Dimillian/Skills/tree/main/gh-issue-fix-flow
- Ref: c579efd02184f1128d6741d16e6c8d951d7d4208
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/dimillian-gh-issue-fix-flow
- Manifest: https://skillstore.pages.dev/api/skills/dimillian-gh-issue-fix-flow/manifest

## Capabilities

- Retrieves GitHub issue details and comments with gh.
- Guides code-path discovery with rg and focused file reads.
- Directs minimal local edits that match repository style.
- Uses XcodeBuildMCP for build and test validation.
- Checks git status before staging selected fix files.
- Creates a closing commit message and pushes the branch.

## Use Cases

- 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.

## Prompt Templates

### Fix One Issue

```
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.
```

### Fix a Specific Repository Issue

```
Use gh-issue-fix-flow for issue 123 in owner/repo. Confirm the repository, read comments, implement the fix, run validation, and summarize changes.
```

### Fix With Targeted Tests

```
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.
```

### Complete and Push a Fix

```
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.
```

## Limitations

- Requires gh authentication and repository access.
- Requires user authorization for local edits, commits, and pushes.
- Best suited to projects that use XcodeBuildMCP validation.
- Does not replace maintainer review or CI policy.

## 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.

## Anti Patterns

- 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.

## Security Audit

- Audited at: 2026-07-05T12:15:38.25\+00:00
- Summary: All 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.

## Stats

- Views: 209
- Downloads: 13
- Favorites: 0
- Popularity score: 0