fix-github-issue

Automate GitHub issue fixes by creating feature branches, running tests, and opening pull requests.

Updated Mar 5, 2026

Search Tags:#automation #workflow #github #issues #pull-request #tests

Ready to run

npx skills add https://github.com/stephanesoares/dotfiles --skill fix-github-issue-stephanesoares

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fix-github-issue
Source: https://github.com/stephanesoares/dotfiles/tree/main/config/claude/skills/fix-github-issue
Command: npx skills add https://github.com/stephanesoares/dotfiles --skill fix-github-issue-stephanesoares

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub issue management can be time-consuming and error-prone; this skill provides a repeatable workflow to fix issues by coding in feature branches, running tests, and creating PRs.

Core Features & Use Cases

Guided workflow to create feature branches named fix-<short-description> and implement the fix
Run local tests (e.g., PHPUnit/Pest) and ensure all tests pass before PR
Open pull requests with conventional commit messages and clear descriptions

Quick Start

Run the fix workflow on a cloned repository to address an issue by creating a feature branch, implementing the fix, running tests, and opening 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 automate GitHub issue fixes with feature branches and pull requests?▼

You can automate GitHub issue fixes by using a guided workflow that creates a feature branch, implements code changes, runs tests, and opens a pull request when tests pass. This requires a local clone and gh CLI authentication.

What do I need to automate issue resolution and open pull requests using gh CLI?▼

To automate issue resolution, you need gh CLI authentication, a local clone of the target repository, a conventional commit style, and a test suite defined in your project configuration to validate changes before opening a pull request.

Can I run local tests before creating a pull request for a GitHub issue fix?▼

Yes, the workflow runs your local test suite, such as PHPUnit or Pest, on the feature branch. It ensures all tests pass before automatically opening a pull request with a conventional commit message and clear description.

How are feature branches named when automating GitHub issue fixes?▼

Feature branches are automatically named using the fix-<short-description> convention. This naming strategy keeps branch history organized while implementing the specific code patch required to resolve the GitHub issue.

Does this workflow support test frameworks other than PHPUnit or Pest?▼

The workflow runs tests defined in your project configuration, mentioning PHPUnit and Pest as examples. As long as your project specifies a test suite execution command, it can validate the feature branch changes before opening a pull request.

What happens if tests fail while fixing a GitHub issue on a feature branch?▼

If tests fail on the feature branch, the workflow stops and prevents opening a pull request. This ensures that only validated code changes with passing tests are submitted for review to resolve the GitHub issue.