fix-github-issue
GitHub Issue Fixer
Fix GitHub issues by implementing solutions on feature branches with proper testing.
Prerequisites
ghCLI installed and authenticated- Repository cloned locally
- Test command available (auto-detected or specified)
Workflow
1. Understand the Issue
gh issue view <issue-number>
Read the issue thoroughly.
2. Create Feature Branch
git checkout main && git pull origin main
git checkout -b fix-<short-description>
Branch naming: fix-description (lowercase, hyphens).
3. Analyze the Codebase
Before coding, understand the relevant parts:
- Locate files related to the issue
- Check existing tests for patterns
- Review any referenced code in the issue
4. Implement the Fix
Make minimal, focused changes that address the issue. Follow existing code style and patterns.
5. Run Tests Locally
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:
- Analyze failures
- Fix the implementation
- Re-run until all pass
6. Commit Changes
git add -A
git commit -m "Fix #<issue-number>: <concise description>"
Use conventional commit message referencing the issue number.
7. Push and Create PR
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>"
8. Monitor CI
gh pr checks --watch
If CI fails:
- Review the failure:
gh run view <run-id> --log-failed - Fix locally
- Push additional commits
- Repeat until CI passes
Quick Reference
# 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 --watch
More from freekmurze/dotfiles
php-guidelines-from-spatie
Describes PHP and Laravel guidelines provided by Spatie. These rules result in more maintainable, and readable code.
144context7-auto-research
Automatically fetches up-to-date documentation from Context7 when users ask about libraries, frameworks, APIs, or need code examples. Triggers proactively without explicit user request.
27react-native-best-practices
Provides React Native performance optimization guidelines for FPS, TTI, bundle size, memory leaks, re-renders, and animations. Applies to tasks involving Hermes optimization, JS thread blocking, bridge overhead, FlashList, native modules, or debugging jank and frame drops.
24agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
24copy-editing
When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' This skill provides a systematic approach to editing marketing copy through multiple focused passes.
24frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
21