fix-issue

Coordinate GitHub bug-fix workflows from issue reproduction to PR creation.

5|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/tomzx/agents --skill fix-issue-tomzx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-issue
Source: https://github.com/tomzx/agents/tree/main/skills/fix-issue
Command: npx skills add https://github.com/tomzx/agents --skill fix-issue-tomzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end bug fixes by coordinating reproduction, implementation, and PR creation from an initial issue through to a merged PR, ensuring repeatable and auditable workflows.

Core Features & Use Cases

  • Duplicate check: scans for existing issues or fix PRs to avoid duplication.
  • Reproduction workflow: fetches the issue, creates a worktree on a fix branch, and attempts to reproduce the bug.
  • Implementation workflow: writes a regression test, adds the fix, and validates the test suite.
  • PR orchestration: pushes the branch and opens a structured PR for review, ensuring proper commit messages and state transitions.
  • Error handling: stops the pipeline at the relevant step if reproduction or implementation fails and posts context.

Quick Start

Invoke the fix-issue workflow with an issue number and optional repository to start the bug-fix sequence.

Frequently Asked Questions about fix-issue

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

FAQPage Schema
How do I automate an end-to-end bug fix workflow on GitHub?

Automating an end-to-end bug fix workflow involves coordinating reproduction, implementation, and pull request creation from a GitHub issue to a merged PR. This ensures repeatable and auditable workflows by managing phase transitions, duplicate checks, and failure modes.

What is the best way to reproduce a GitHub issue locally before writing a fix?

Reproducing a GitHub issue locally requires fetching the issue details, creating a Git worktree on a fix branch, and attempting to replicate the bug. If reproduction fails, the automated pipeline stops and posts context to prevent invalid fixes.

Does this bug fix automation work with my existing GitHub CLI and Git worktree setup?

Yes, this bug fix automation requires the GitHub CLI with write access and Git worktree support to function. It also needs access to SDLC context files to properly orchestrate the implementation and pull request creation steps.

How do I prevent duplicate pull requests when fixing GitHub issues?

Preventing duplicate pull requests involves scanning for existing issues or fix PRs before starting the workflow. This duplicate check runs initially to avoid redundant work and ensures the bug fix pipeline only proceeds for novel issues.

What happens if a regression test fails during automated bug fix implementation?

If a regression test fails during implementation, the bug fix pipeline stops at the relevant step and posts context about the failure. This error handling prevents invalid code from being pushed and opening a pull request.

How to create a structured pull request after writing a bug fix?

Creating a structured pull request after a bug fix involves pushing the fix branch and opening a PR for review with proper commit messages. The automation ensures correct state transitions throughout the implementation and PR orchestration workflow.