skills.rest
whywaita
whywaitaCOMMUNITY
Explore all skills by this author →
Website𝕏@whywaitaGitHub

fix-github-issue

Investigate GitHub issues with gh, implement minimal fixes, and open PRs.

Updated Oct 29, 2013
Search Tags:#github#issue#gh#pull-request#bug-fix#tests
One-click install
npx skills add https://github.com/whywaita/dotfiles --skill fix-github-issue-whywaita
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-github-issue
Source: https://github.com/whywaita/dotfiles/tree/main/dot_codex/skills/fix-github-issue
Command: npx skills add https://github.com/whywaita/dotfiles --skill fix-github-issue-whywaita

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate and fix a GitHub issue by using gh to view the issue and its comments, reproduce the bug, implement a minimal fix, and validate with tests before opening a PR.

Core Features & Use Cases

  • Reproduce issues using gh issue view and gather context from comments and labels.
  • Locate and fix the root cause with minimal scope changes, then update tests and lint as needed.
  • Open a PR following the repository's workflow to validate the fix and collaborate with maintainers.

Quick Start

View the issue with gh issue view, reproduce the bug, implement a minimal fix, run tests, and open a PR.

Frequently Asked Questions about fix-github-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a GitHub issue and automatically create a pull request?▼

You can fix a GitHub issue by viewing the issue and comments with gh, reproducing the bug, implementing a minimal fix, running tests and linting, and then opening a PR. This workflow reads the issue, restates the problem, locates relevant code, and validates changes before pushing.

What's the best way to reproduce a bug from a GitHub issue before patching it?▼

The best way to reproduce a bug from a GitHub issue is to use gh issue view to gather context from comments and labels. After reproducing the issue, locate the root cause, implement minimal code changes, update tests, and run lint or type checks before submitting a PR.

Can I use gh to investigate issue comments and locate the relevant code for a bug fix?▼

Yes, you can use gh to view an issue and its comments to gather context. After reading and restating the problem, the workflow involves searching the codebase to locate relevant code, implementing a minimal scope fix, and running tests to validate the change before opening a PR.

Does fixing a GitHub issue with this workflow include running tests and lint checks?▼

Yes, fixing a GitHub issue with this workflow includes running tests and lint or type checks. After implementing the minimal fix to resolve the root cause, the process requires validating with tests and linting before opening a properly described pull request for maintainers.

How do I ensure my GitHub bug fix PR follows the repository's commit and push workflow?▼

To ensure your bug fix PR follows the repository workflow, implement minimal scope changes after locating the root cause, validate with tests and linting, then create a properly described PR. This commit-push-pr workflow collaborates with maintainers by safely validating the investigated fix.

Related Skills

Explore More Software Engineering Skills→
freekmurzefreekmurze
997

fix-github-issue

Automate GitHub issue fixes on feature branches with local tests and PR creation.

Community
Advanced
chroniicallydiistractedchroniicallydiistracted

source-command-review-pull-request

Review unanswered GitHub Pull Request comment threads and apply changes.

Community
Advanced
FilenCloudDiensteFilenCloudDienste
87

verify-changes

Execute ESLint, TypeScript checks, and unit tests on code changes.

Official
Intermediate
jonkikyjonkiky

investigate

Trace reported issue symptoms to code paths and verify root cause hypotheses.

Community
Advanced