fix-issue

Reproduce GitHub issues end-to-end and fix them with test-driven development.

11|Updated Sep 5, 2025

Search Tags:#tdd #github #worktree #issue #reproduce #code-review #ci

Ready to run

npx skills add https://github.com/thrawn01/claude-dotfiles --skill fix-issue-thrawn01

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fix-issue
Source: https://github.com/thrawn01/claude-dotfiles/tree/main/skills/fix-issue
Command: npx skills add https://github.com/thrawn01/claude-dotfiles --skill fix-issue-thrawn01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill orchestrates end-to-end GitHub issue handling—from parsing and classification to reproducibility assessment, worktree creation, code exploration, testing, implementation via TDD, self-review, PR submission, and CI babysitting.

Core Features & Use Cases

Phase-driven orchestration: parses issues, determines type, and delegates work to sub-agents for reproducibility, exploration, and implementation.
End-to-end workflow: creates isolated worktrees, writes surface tests, and ensures CI stays green.
Use Case: When a maintainer needs a reproducible fix for a bug or a complete feature implementation with verification.

Quick Start

Provide a GitHub issue URL or number to trigger an end-to-end reproduce-and-fix workflow.

Frequently Asked Questions about fix-issue

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

FAQPage Schema

How do I automate fixing a GitHub issue end-to-end from reproduction to PR?▼

You can automate GitHub issue resolution by triggering a phase-driven workflow that parses the issue, creates an isolated worktree, reproduces the bug, writes surface tests, implements a fix via TDD, and submits a PR.

How does TDD apply to resolving GitHub issues automatically?▼

TDD in GitHub issue resolution involves writing surface tests to reproduce the bug first, then implementing the code fix to pass those tests, followed by self-review and CI verification before PR submission.

Can I use Git worktrees to isolate GitHub issue fixes?▼

Yes, the workflow creates an isolated Git worktree for each GitHub issue, allowing you to explore the codebase and implement TDD fixes without affecting your main branch.

What's the best way to ensure CI passes before merging a GitHub issue fix?▼

The best way is to use a workflow that babysits CI after submitting the PR, ensuring the automated TDD fix and surface tests keep the CI pipeline green until the issue is fully resolved.

Do I need to provide a GitHub issue URL to start the reproduce and fix workflow?▼

Yes, you trigger the end-to-end reproduce-and-fix workflow by providing a GitHub issue URL or issue number, which the system parses to assess type and reproducibility.

Why should I use an automated workflow instead of manually fixing GitHub issues?▼

An automated workflow ensures end-to-end consistency by handling reproducibility assessment, codebase exploration, TDD implementation, self-review, and CI monitoring, reducing manual oversight for maintainers.