github-issue-fix-flow

Implements fixes for GitHub issues from intake through commit and push using gh CLI and git.

3|Updated Jun 15, 2026
One-click install
npx skills add https://github.com/patrickserrano/lacquer --skill github-issue-fix-flow-patrickserrano
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-issue-fix-flow
Source: https://github.com/patrickserrano/lacquer/tree/main/core/skills/github-issue-fix-flow
Command: npx skills add https://github.com/patrickserrano/lacquer --skill github-issue-fix-flow-patrickserrano

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Resolving a GitHub issue involves many manual steps: reading the issue, locating the relevant code, implementing a fix, building and testing, and committing with the right closing message. This Skill standardizes that entire end-to-end workflow so nothing is skipped and every fix is validated before it is pushed. ## Core Features & Use Cases - Issue Intake: Pulls full issue context with gh issue view <id> --comments, capturing reproduction steps, expected behavior, and maintainer notes. - Guided Fix Workflow: Locates the code path with ripgrep, implements minimal changes aligned with repo conventions, and runs builds and tests (including Swift/Xcode commands). - Clean Commit and Push: Stages only relevant files, commits with a Closes #<id> message, pushes, and optionally opens a PR with gh pr create --fill. - Use Case: A maintainer assigns you issue #123 reporting a crash. Use this Skill to read the issue, find the failing code path, implement and test the fix, then commit with "Closes #123" and push — all following a consistent checklist. ## Quick Start Take GitHub issue number 123, implement a fix for it, run the build and tests, then commit with a closing message and push the changes.

Frequently Asked Questions about github-issue-fix-flow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a GitHub issue from the command line?▼

Use gh issue view <id> --comments to read the full issue context, locate the relevant code with ripgrep, implement the fix, run builds and tests, then commit with a message containing Closes #<id> and push with git.

How to automatically close a GitHub issue with a commit?▼

Include Closes #<issue number> in the commit message body, for example git commit -m "Fix: description\n\nCloses #123". When the commit is pushed to the default branch or merged via PR, GitHub closes the issue automatically.

Does this workflow support Swift and Xcode projects?▼

Yes, the workflow includes Swift and Xcode build and test commands such as swift build, swift test, and xcodebuild with scheme and destination flags. For other project types, the appropriate build and test commands are used instead.

How do I create a pull request for an issue fix using gh CLI?▼

Create a branch like fix/issue-<id>, commit your changes, push with git push -u origin HEAD, then run gh pr create --fill to open a pull request populated from your commits. This is the optional PR path in the workflow.

Why should I stage only specific files instead of git add all?▼

Staging only the files related to the fix prevents unrelated local changes from being included in the commit. Check git status --short and git diff first to identify unrelated modifications before staging.