resolve-issues-ag

Triage GitHub issues and propose per-issue fix plans for user validation.

44.0k|5.9k|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/diegosouzapw/OmniRoute --skill resolve-issues-ag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolve-issues-ag
Source: https://github.com/diegosouzapw/OmniRoute/tree/main/.agents/skills/resolve-issues-ag
Command: npx skills add https://github.com/diegosouzapw/OmniRoute --skill resolve-issues-ag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It streamlines resolving open GitHub issues by automatically triaging, proposing fixes with per-issue isolation, and waiting for explicit user approval before any code changes land.

Core Features & Use Cases

  • Open-issue discovery and bug-focused triage: Fetches all open issues, classifies them, and only plans work for issues identified as bugs.
  • PR-linked safety policy: Detects issues that already have contributor PRs so it can redirect instead of re-implementing and accidentally duplicating work.
  • Controlled fix implementation workflow: For approved fixes, creates a dedicated worktree and short-lived branch per issue, writes regression tests first, implements the change, opens a PR into the release branch, then cleans up.

Quick Start

Ask an agent to run the resolve-issues-ag workflow for your repository and to propose up to 30 bug fixes per batch, pausing for your OK before implementing any changes.

Frequently Asked Questions about resolve-issues-ag

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

FAQPage Schema
How do I automatically batch fix GitHub issues without duplicating existing contributor work?

To batch fix GitHub issues without duplicating work, use an automated triage workflow that detects issues with existing contributor pull requests and redirects them instead of re-implementing the fix. This prevents accidental duplication during repository maintenance.

Can I resolve GitHub bug reports using isolated worktrees and test-driven development?

Yes, you can resolve GitHub bug reports using isolated worktrees by creating a dedicated worktree and short-lived branch per issue. The workflow enforces test-driven development by writing regression tests first prior to implementing the actual code changes.

What is the best way to triage open GitHub issues and prepare per-issue fix plans?

The best way to triage open GitHub issues and prepare fix plans is to fetch all open issues, classify them, and only plan work for issues explicitly identified as bugs. The system then prepares per-issue fix plans that require your explicit validation before any code changes.

Does resolving GitHub bugs with an automated workflow require manual approval before merging code?

Yes, resolving GitHub bugs with this automated workflow requires manual approval before merging code. The system pauses for your explicit OK before implementing any changes, ensuring you validate the proposed fix plans before code lands in the release branch via pull requests.

What are the limitations when batch resolving GitHub bug reports with an automated workflow?

Limitations when batch resolving GitHub bug reports include capping to 30 issues per batch and requiring reliable fetching of issue metadata. The workflow also strictly enforces PR-linked redirection, meaning it will not process issues that already have open contributor pull requests.

Can I communicate GitHub bug fix resolutions in the original issue reporter's language?

Yes, you can communicate GitHub bug fix resolutions in the original issue reporter's language. The workflow optionally translates and communicates the fix details in the reporter's language when opening pull requests into the designated release branch.