Fix GitHub issues using gh CLI. Use when asked to fix, resolve, or address a GitHub issue. Creates fixes on separate branches, runs tests locally, and creates PRs when tests pass. Requires gh CLI authenticated and repo cloned locally.
100
Quality
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Fix GitHub issues by implementing solutions on feature branches with proper testing.
gh CLI installed and authenticatedgh issue view <issue-number>Read the issue thoroughly.
git checkout main && git pull origin main
git checkout -b fix-<short-description>Branch naming: fix-description (lowercase, hyphens).
Before coding, understand the relevant parts:
Make minimal, focused changes that address the issue. Follow existing code style and patterns.
Detect and run the test suite. Most likely it will be pest or phpunit. Take a look what is defined in composer.json or the testing github file.
Tests must pass locally before proceeding. If tests fail:
git add -A
git commit -m "Fix #<issue-number>: <concise description>"Use conventional commit message referencing the issue number.
git push -u origin fix/issue-<issue-number>-<short-description>
gh pr create --title "Fix #<issue-number>: <title>" --body "Fixes #<issue-number>
## Changes
- <bullet points of changes>
## Testing
- All local tests pass
- <any additional testing done>"gh pr checks --watchIf CI fails:
gh run view <run-id> --log-failed# View issue
gh issue view 123
# Create branch
git checkout -b fix/issue-123-description
# After fixing and tests pass
git add -A && git commit -m "Fix #123: description"
git push -u origin fix/issue-123-description
gh pr create --fill
# Watch CI
gh pr checks --watch355d067
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.