auto-issue-fixer

To automate fixing GitHub issues end-to-end, you need a workflow that triages open issues, implements fixes using TDD, generates PRs, and monitors CI. This skill automates that complete lifecycle autonomously, including handling bot reviews and posting completion notifications.

Yes, you can automate TDD implementation for GitHub issues. This skill builds tests first, then code, creating automated feedback loops that generate pull requests and monitor CI status until completion.

Yes, you need gh, git, and jq installed to automate GitHub issue resolution. These dependencies are required for the skill to interact with repositories, manage Git operations, and parse JSON data during the automated workflow.

An automated GitHub issue fixer handles CI checks and bot reviews through a bot-review-aware feedback loop. It monitors CI status, processes review feedback, and manages human input to ensure pull requests meet repository requirements before completion.

The best way to triage and prioritize open GitHub issues automatically is using a multi-phase workflow with parallel subagents. This approach discovers issues, prioritizes them, and implements fixes sequentially while providing phase-based status updates.

Yes, you can specify a single GitHub issue number for automated fixing. By providing an ISSUE_NUMBER parameter, the skill operates exclusively on that specific issue rather than processing the next open issue in the repository.