skills.rest
jonball4
jonball4COMMUNITY
Explore all skills by this author →
GitHub

bugfix-v2

Orchestrates a 6-phase bug-fixing workflow from discovery to automated pull request creation.

1|Updated Jan 27, 2026
Search Tags:#automation#tdd#debugging#pull request#root cause analysis#bugfix
One-click install
npx skills add https://github.com/jonball4/claude-dev-skills --skill bugfix-v2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bugfix-v2
Source: https://github.com/jonball4/claude-dev-skills/tree/main/skills/bugfix-v2
Command: npx skills add https://github.com/jonball4/claude-dev-skills --skill bugfix-v2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the entire bug-fixing process, from identifying the root cause to creating a well-documented pull request, ensuring bugs are fixed efficiently and thoroughly.

Core Features & Use Cases

  • 6-Phase Workflow: Orchestrates Discovery, Root Cause Analysis, Solution Design, Execution, Review, and Handoff.
  • Root Cause Analysis: Dedicated phase for debugging and pinpointing the exact source of the bug.
  • TDD Execution: Implements fixes using Test-Driven Development with regression tests.
  • Automated PR Creation: Generates comprehensive pull requests including root cause documentation.
  • Use Case: When a critical bug is reported in Jira (e.g., BUG-456), this skill can be invoked to systematically debug, fix, test, and create a PR for it.

Quick Start

Use the bugfix-v2 skill to start fixing the bug associated with ticket BUG-456.

Frequently Asked Questions about bugfix-v2

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

FAQPage Schema
How do I automate systematic debugging and bug fixing for Jira tickets?▼

Automated bug fixing for Jira tickets is orchestrated through a 6-phase workflow encompassing discovery, root cause analysis, solution design, TDD-based execution, review, and automated pull request creation with root cause documentation.

What is the best way to document root cause analysis in a pull request?▼

Documenting root cause analysis in a pull request is handled automatically during the handoff phase, generating comprehensive PRs that include dedicated root cause documentation alongside the applied TDD-based code fixes.

How do I fix bugs using TDD with automated regression testing?▼

Fixing bugs using TDD with automated regression testing occurs during the execution phase, where solutions are implemented using Test-Driven Development principles to ensure thorough fixes and prevent future regressions.

Can I use this automated bugfix workflow with GitHub and Jira?▼

This automated bugfix workflow integrates directly with Jira for ticket management and GitHub for code changes, streamlining the process from bug discovery through automated pull request creation.

What are the phases of a systematic debugging workflow?▼

The phases of a systematic debugging workflow include Discovery, Root Cause Analysis, Solution Design, Execution, Review, and Handoff, ensuring complex bug scenarios are systematically debugged and regression tested.

Does automated bug fixing require a specific ticket format to start?▼

Automated bug fixing requires a Jira ticket identifier, such as BUG-456, to invoke the skill and begin the systematic process of debugging, fixing, testing, and creating a pull request for the reported issue.

Related Skills

Explore More Software Engineering Skills→
8GG-Git8GG-Git

fix-ticket

Automate Jira bug fixing from ticket analysis through commit and status updates.

Community
Advanced
gittowergittower
413

quick-fix

Resolve small local maintenance tasks with test-first implementation and Codex review.

Official
Advanced
deanobalinodeanobalino

Testing Skill

Execute automated test suites and analyze failures across detected frameworks.

Community
Intermediate
CarbeneAICarbeneAI
9

investigate

Guide root-cause debugging through investigation, analysis, hypothesis, and implementation phases.

Community
Advanced