fix-github-issue

Plan, implement, and submit a GitHub issue fix via a dedicated git worktree.

1|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/vultuk/coding-agent-skills --skill fix-github-issue-vultuk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-github-issue
Source: https://github.com/vultuk/coding-agent-skills/tree/main/fix-github-issue
Command: npx skills add https://github.com/vultuk/coding-agent-skills --skill fix-github-issue-vultuk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the end-to-end process of fixing a GitHub issue by creating a dedicated worktree, loading issue context, planning the implementation, applying changes, and submitting a PR that references the issue.

Core Features & Use Cases

  • Isolates changes with a dedicated git worktree to keep the main repository clean.
  • Loads issue details and related PRs to inform implementation.
  • Generates a planning guide and automates commit and PR creation.

Quick Start

Run the skill with an issue number, for example: fix-github-issue 123. The skill will set up the worktree, load issue context, propose a plan, implement changes, and open a PR linked to the issue. Ensure you are authenticated with gh and that the repository has an origin remote.

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 fixing a GitHub issue and opening a pull request from start to finish?

You can automate fixing a GitHub issue end-to-end by providing the issue number, which triggers a workflow that creates a dedicated git worktree, loads issue context, plans the implementation, applies changes, and submits a linked PR.

How do git worktrees keep my main repository clean when implementing issue fixes?

Git worktrees isolate changes for an issue fix in a separate directory, preventing conflicts with your main repository branch while allowing automated context loading, implementation, and PR submission.

Do I need the gh CLI and git installed to automate GitHub issue fixes and PR creation?

Yes, automating GitHub issue fixes and PR creation requires both the git and gh CLI tools installed, and you must be authenticated with gh while ensuring the repository has an origin remote configured.

What is the best way to load GitHub issue context before planning an implementation?

The best way to load GitHub issue context is through an automated script that retrieves issue details and related PRs, informing the implementation plan before applying changes in an isolated git worktree.

Can I submit a pull request that automatically references a specific GitHub issue number?

Yes, you can submit a pull request that automatically references a specific GitHub issue number, linking the PR directly to the issue after applying changes within a dedicated git worktree.

What happens if my repository does not have an origin remote when automating issue fixes?

Automating issue fixes requires a configured origin remote to interact with GitHub via gh. Without it, the workflow cannot load issue context or create and submit the pull request.