fix-issue

Analyze a GitHub issue, implement a fix, and create a pull request.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/simplerick0/com.ackhax.configs --skill fix-issue-simplerick0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-issue
Source: https://github.com/simplerick0/com.ackhax.configs/tree/main/skills/fix-issue
Command: npx skills add https://github.com/simplerick0/com.ackhax.configs --skill fix-issue-simplerick0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers and maintainers automatically analyze a GitHub issue, implement a code fix following project patterns, and open a pull request to merge the change.

Core Features & Use Cases

  • Automatically fetch and interpret the issue details to determine scope.
  • Create a dedicated fix branch named fix/issue-<number>.
  • Implement the fix following repository conventions and patterns.
  • Commit with a descriptive message referencing the issue number.
  • Create a PR to merge the fix back into the main branch.

Quick Start

Provide an issue number to begin the workflow. Example: fix-issue 123

Frequently Asked Questions about fix-issue

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

FAQPage Schema
How do I automatically fix GitHub issues by creating a pull request?

To automatically fix GitHub issues, you provide an issue number to trigger a workflow that fetches the issue, creates a dedicated branch, implements the code fix, and opens a pull request using the GitHub CLI.

Can I automate branch creation and PR generation directly from an issue number?

Yes, you can automate PR generation from an issue number by initiating a deterministic process that creates a branch named fix/issue-<number>, commits the code changes, and submits the pull request automatically.

What is the best way to ensure my automated code fix follows existing repository conventions?

The best way to ensure an automated code fix follows repository conventions is to use a workflow that analyzes the GitHub issue details and interprets project patterns before implementing the corresponding code changes.

Do I need the GitHub CLI to automatically create a PR for a code fix?

Yes, you need the GitHub CLI to automatically create a PR for a code fix, as the workflow relies on it to submit the pull request and merge the branch back into the main branch.

How does the automated workflow reference the original issue in the commit history?

The automated workflow references the original issue in the commit history by generating a descriptive commit message that explicitly includes the issue number before creating the pull request.

Are there limitations to automatically fixing GitHub issues with an automated branch and PR workflow?

A limitation of automatically fixing GitHub issues is that the workflow requires a specific issue number to start, meaning it cannot infer scope from vague descriptions or implement fixes without a tracked GitHub issue.