Menu
Automatically fix GitHub issues labeled as 'bug'. Fetches bug issues, analyzes them, implements fixes, and creates PRs against the main branch.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
ArgoCD deployment and rollback operations
ArgoCD application management, sync operations, and GitOps troubleshooting
Database debugging and query execution
Docker container management and troubleshooting
Git repository operations and troubleshooting
HTTP API testing and debugging
| name | bugfix |
| description | Automatically fix GitHub issues labeled as 'bug'. Fetches bug issues, analyzes them, implements fixes, and creates PRs against the main branch. |
Automates the bug fixing workflow by:
When invoked, this skill will:
# List all open bug issues
gh issue list --label "bug" --state open --json number,title,body,labels,createdAt --limit 20
For each bug issue, analyze:
# Create a branch for the fix
git checkout -b fix/issue-<number>-<short-description>
# Stage and commit changes
git add -A
git commit -m "fix: <description> (fixes #<issue-number>)"
# Push and create PR
git push -u origin fix/issue-<number>-<short-description>
gh pr create \
--title "fix: <description>" \
--body "## Summary
Fixes #<issue-number>
## Changes
- <change 1>
- <change 2>
## Testing
- [ ] Unit tests pass
- [ ] Manual testing completed
## Checklist
- [ ] Code follows project style
- [ ] Tests added/updated
- [ ] Documentation updated if needed"
When this skill is invoked, follow these steps:
gh repo view --json owner,name,defaultBranchRef
gh issue list --label "bug" --state open --json number,title,body,createdAt,url --limit 10
a) Read the issue details:
gh issue view <number> --json title,body,comments
b) Create a fix branch:
git checkout main
git pull origin main
git checkout -b fix/issue-<number>-<short-slug>
c) Analyze and implement:
d) Verify the fix:
# For Rust projects
cargo test
cargo clippy
# For Node projects
npm test
npm run lint
e) Commit and push:
git add -A
git commit -m "fix: <description>
Fixes #<issue-number>"
git push -u origin fix/issue-<number>-<short-slug>
f) Create the PR:
gh pr create --base main --title "fix: <title>" --body "<body>"
If multiple bug issues exist, present them to the user:
Found N open bug issues:
1. #123 - Login fails with special characters
Created: 2 days ago
2. #118 - API returns 500 on empty request
Created: 5 days ago
3. #115 - Memory leak in worker process
Created: 1 week ago
Which issue would you like to work on? (Enter number or 'all' for batch mode)
Use this template for bug fix PRs:
## Summary
Fixes #<issue-number>
## Problem
<Brief description of the bug>
## Solution
<Description of the fix and why it works>
## Changes
- <File 1>: <What changed>
- <File 2>: <What changed>
## Testing
- [ ] Existing tests pass
- [ ] New tests added for the fix
- [ ] Manually verified the fix
## Screenshots/Logs
<If applicable, add before/after screenshots or log output>
# Check if label exists
gh label list | grep -i bug
# Create bug label if missing
gh label create bug --color d73a4a --description "Something isn't working"
# Check gh auth status
gh auth status
# Re-authenticate if needed
gh auth login
# Delete local branch and recreate
git branch -D fix/issue-<number>-<slug>
git checkout -b fix/issue-<number>-<slug>