fix-github-issue_skill

Overview

This skill fixes GitHub issues using the gh CLI by creating focused feature branches, running tests locally, and opening pull requests when tests pass. It is designed for repositories cloned locally with gh authenticated and a working test command. The workflow enforces small, test-backed changes and CI monitoring to ensure reliable fixes.

How this skill works

I inspect the issue via gh issue view, create a dedicated fix branch from main, implement a minimal change that follows project style, and run the local test suite until all tests pass. I commit with a conventional message referencing the issue, push the branch, create a PR with a descriptive body, and watch CI checks until they succeed. If tests or CI fail, I iterate locally until green.

When to use it

• When asked to fix, resolve, or address a specific GitHub issue in a repo cloned locally.
• When you have gh CLI installed and authenticated for the target GitHub account.
• When the repository includes a test command that can be run locally.
• When you want changes isolated on a dedicated branch and tracked by a PR.
• When you need to ensure CI passes before merging a fix.

Best practices

• Pull latest main before creating the fix branch and use clear hyphenated branch names like fix/issue-123-short-desc.
• Make minimal, focused changes that directly address the issue and follow existing style and patterns.
• Run the full test suite locally and fix all failures before pushing changes.
• Reference the issue number in commit messages and PR titles (e.g., Fix #123: concise description).
• Use gh pr create --fill or a detailed body listing changes and testing performed.
• Monitor CI with gh pr checks --watch and iterate until CI is green.

Example use cases

• Fix a shell prompt bug in my dotfiles where zsh option causes incorrect behavior; run local zsh checks and open a PR.
• Resolve a Vimscript mapping conflict reported in an issue by editing the relevant vimrc file, running any available lint/tests, and creating a PR.
• Address a broken install script by adding a guard and unit test, then push a fix branch and create a PR.
• Update documentation referenced by an issue, ensure any docs-build tests pass, and submit the PR for review.
• Refactor a small function to fix a regression, run tests locally, and open a PR that references the issue.