bug-fixer

Automate bug fixing from unassigned GitHub issues using TDD and worktrees.

Updated Aug 23, 2026

Search Tags:#automation #github #worktree #issue-tracking #pull-request #test-driven-development #bug-fix

Ready to run

npx skills add https://github.com/satriachandrayw/skills --skill bug-fixer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bug-fixer
Source: https://github.com/satriachandrayw/skills/tree/main/bug-fixer/skills/bug-fixer
Command: npx skills add https://github.com/satriachandrayw/skills --skill bug-fixer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates end-to-end bug fixing by reading GitHub issues without an assigned label, implementing fixes in isolated worktrees following TDD, and creating PRs that reference the issues.

Core Features & Use Cases

Fetch unassigned issues from GitHub and claim them by applying the assigned label to prevent duplicate work.
Set up isolated worktrees for each fix, run tests, and implement fixes following the TDD workflow.
Batch low-severity issues into a single PR while creating individual PRs for medium/high severity, with audit logs updated on completion.

Quick Start

Run the /bug-fixer command with the target issue numbers to begin the fix.

Frequently Asked Questions about bug-fixer

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

FAQPage Schema

How do I automate bug fixes from GitHub issues using TDD?▼

Automated bug fixing reads unassigned GitHub issues, implements fixes in isolated worktrees following test-driven development, and creates pull requests referencing the issues. It claims work by applying the assigned label to prevent duplicates, then updates the audit log upon completion.

What's the best way to batch low-severity bug reports into a single pull request?▼

Batching low-severity issues into a single PR is handled automatically during the bug fix workflow, while medium and high severity issues receive individual PRs. The system reads unassigned GitHub issues, sets up isolated worktrees, and groups fixes based on severity.

Do I need Git and the GitHub CLI to automate pull request creation for bug reports?▼

Yes, automating pull request creation for bug reports requires Git, the GitHub CLI, and a test framework. These tools enable the workflow to claim issues via labels, create isolated worktrees, run tests, and submit PRs that reference the original issues.

How does test-driven development work when fixing bugs in isolated Git worktrees?▼

Test-driven development in isolated Git worktrees involves setting up a separate working directory for each bug fix, running tests, and implementing the fix to satisfy the test suite. This ensures fixes are validated before a pull request is created.

Can I prevent duplicate work when automating GitHub issue tracking and bug fixes?▼

Preventing duplicate work is achieved by applying the assigned label to GitHub issues immediately after fetching them. This label workflow claims the issue, ensuring no other automated processes or developers attempt to fix the same bug simultaneously.

When should I not use automated TDD-driven bug fixing for my repository?▼

Automated TDD-driven bug fixing may not suit repositories lacking a test framework or issues without clear severity labels. It depends on structured, unassigned bug reports and requires Git and the GitHub CLI to manage worktrees and pull requests effectively.