fix-github-issue

whywaita's avatarfrom whywaita

Investigate and fix a GitHub issue using gh, then validate with tests and create a PR. Use when a user references a GitHub issue number or asks to fix an issue.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 10, 2026
[Debugging]

When & Why to Use This Skill

The fix-github-issue skill automates the end-to-end lifecycle of resolving software defects. By integrating the GitHub CLI (gh) with intelligent code analysis, it streamlines the process of investigating issue reports, implementing precise code fixes, and validating changes through automated testing before submitting a professional pull request.

Use Cases

  • Automated Bug Resolution: Rapidly address software bugs reported by users by allowing the agent to analyze the issue context, locate the faulty logic, and apply a fix automatically.
  • Continuous Integration Workflow: Enhance the development pipeline by automating the repetitive tasks of running linters, type checks, and unit tests before PR submission.
  • Open Source Maintenance: Efficiently manage high volumes of community-reported issues by automating the initial investigation and drafting pull requests for maintainer review.
  • Test-Driven Development (TDD) Support: Ensure every bug fix is backed by regression tests by automatically generating and updating test suites to cover the reported failure paths.
namefix-github-issue
descriptionInvestigate and fix a GitHub issue using gh, then validate with tests and create a PR. Use when a user references a GitHub issue number or asks to fix an issue.

Fix GitHub Issue

Workflow

  1. Read the issue with gh issue view (include comments and labels as needed).
  2. Restate the problem and expected behavior succinctly.
  3. Search the codebase for relevant files and logic.
  4. Implement the fix with minimal scope changes.
  5. Add or update tests to cover success and failure paths.
  6. Run tests, lint, and type checks appropriate to the repo.
  7. Create a commit and PR following the commit-push-pr workflow.

Notes

  • Use gh for all GitHub interactions (issues, PRs, checks).
  • If the issue lacks repro steps, add a small reproduction section in the PR notes.