github-fix-issue

Automate GitHub issue fixes from analysis to pull request using the GitHub CLI.

2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/billlzzz26/note-taker-convex-ai-convex --skill github-fix-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-fix-issue
Source: https://github.com/billlzzz26/note-taker-convex-ai-convex/tree/main/.agents/skills/github-fix-issue
Command: npx skills add https://github.com/billlzzz26/note-taker-convex-ai-convex --skill github-fix-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end GitHub issue fixes from analysis to PR streamlines the repair workflow, reducing manual handoffs and speeding delivery.

Core Features & Use Cases

  • Analyze issue details with gh issue view
  • Research the codebase for related context and prior PRs
  • Plan the fix and create a branch
  • Implement changes with incremental commits
  • Test changes and open a PR with clear messaging

Quick Start

Provide the GitHub issue number or URL and a brief description of the bug, and I will start the end-to-end fix workflow

Frequently Asked Questions about github-fix-issue

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

FAQPage Schema
How do I automate GitHub bug fixes from issue analysis to pull request?

To automate GitHub bug fixes from issue analysis to pull request, you provide an issue number or URL, and the workflow guides the process from branch creation and incremental commits to testing and PR submission using the gh CLI.

Do I need the GitHub CLI installed to automate issue triage and pull requests?

Yes, automating issue triage and pull requests requires the GitHub CLI (gh) installed and authenticated, as it uses gh issue view to analyze context and opens the final PR through command-line operations.

What is the process for creating a feature branch for a specific GitHub issue?

Creating a feature branch for a specific GitHub issue involves generating a branch named fix/issue-<number>, implementing code changes with enforced small commits, and documenting updates before opening the pull request.

Can I use an issue description instead of an issue number to start the fix workflow?

Yes, you can use an issue description instead of an issue number to start the fix workflow, as the automation accepts issues identified by number, URL, or description to analyze context and plan code changes.

How does the automated workflow research the codebase before planning a bug fix?

The automated workflow researches the codebase before planning a bug fix by analyzing issue details with gh issue view and searching for related context and prior PRs to ensure accurate code modifications.