fix-issues

Scan open bug issues, apply code fixes, and open pull requests.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mitchlabeetch/Largarda --skill fix-issues-mitchlabeetch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-issues
Source: https://github.com/mitchlabeetch/Largarda/tree/main/.agents/skills/fix-issues
Command: npx skills add https://github.com/mitchlabeetch/Largarda --skill fix-issues-mitchlabeetch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically fetches open bug issues labeled as bugs, analyzes feasibility, applies targeted code fixes, and submits pull requests, enabling hands-off bug resolution at scale.

Core Features & Use Cases

  • Automated triage of bug issues based on body content and linked PRs.
  • Single-issue PRs per invocation with deterministic fixes and CI-ready changes.
  • Daemon mode for continuous background processing of new issues as they arrive.

Quick Start

Run /fix-issues to start an automated bug-fix cycle against the configured repository.

Frequently Asked Questions about fix-issues

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

FAQPage Schema
How do I automatically fix GitHub bugs and open pull requests?

You can automatically fix GitHub bugs by running an automated bug-fix cycle that scans open issues labeled as bugs, applies targeted code fixes, and submits pull requests. This process requires a functioning gh CLI.

Can I process bug issues continuously in the background?

Yes, you can process bug issues continuously by enabling daemon mode. This allows the automated bug-fix cycle to run in the background, continuously processing new bug issues as they arrive in the configured repository.

Does the automated bug triage check for existing linked PRs before fixing?

Yes, automated bug triage analyzes issue body content and checks for linked PRs before applying fixes. This ensures each bug fix is isolated to a single root cause per branch and prevents duplicate pull requests.

Do I need to run tests and lint checks before creating an automated bug fix PR?

Yes, the automated bug fix process enforces tests, lint, and type checks before pull request creation. This ensures all code changes are CI-ready and meet repository quality standards before submission.

How many bug issues are fixed per invocation?

The automated bug fix process handles one issue per invocation. This ensures deterministic fixes by isolating changes to a single root cause per branch before opening a pull request.

What is the best way to scale bug resolution for a GitHub repository?

The best way to scale bug resolution is to run automated bug-fix cycles against a configured repository. This fetches open bug issues, analyzes feasibility, applies targeted code fixes, and submits pull requests for hands-off resolution.