resolve-issues-cx

Classify GitHub issues, analyze bug root causes, and prepare fix plans with regression tests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams automatically triage and resolve existing GitHub issues by first classifying bugs, analyzing root causes, and then preparing fixes that are only implemented after user approval to avoid accidental breakage.

Core Features & Use Cases

  • Issue discovery & triage: Fetches all open issues in bounded batches, classifies them, and focuses resolution effort on Bugs while skipping Feature Requests and Questions with notes.
  • PR-linked safety: Detects whether a bug already has a linked open contributor PR and redirects work instead of re-implementing.
  • Worktree-based per-issue fixes: Creates an isolated git worktree and fix/<issue>-<short> branch per bug, writes a regression plan, waits for approval, then generates tests, commits, opens a PR into the release branch, merges, and cleans up.
  • Controlled change management: Enforces the “never commit directly to the release branch” rule and batches up to 30 issues per run with staged validation.

Quick Start

Use the resolve-issues-cx skill to prepare a user-approved batch of up to 30 bug fixes by fetching open GitHub issues, analyzing them, producing a report, and then only implementing fixes after you confirm.

Frequently Asked Questions about resolve-issues-cx

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

FAQPage Schema
How do I batch fix GitHub bugs on a release branch without committing directly to it?

To batch fix GitHub bugs without direct commits, use isolated git worktrees to create short-lived fix branches that merge into the release branch via pull requests. This enforces strict branch lifecycle rules and safe guardrails.

What is the safest way to triage open GitHub issues and prepare bug fixes for regression testing?

Safe issue triage fetches open GitHub issues in bounded batches, classifies bugs while skipping non-bugs, and prepares per-issue fix work plans with regression tests. Implementation only proceeds after explicit user validation gating.

Can I automatically resolve GitHub issues that already have an open pull request?

You should not automatically resolve GitHub issues with an open linked contributor pull request. The workflow detects PR-linked issues and redirects work to avoid re-implementing existing fixes.

How many GitHub issues can I analyze and fix in a single batch run?

You can analyze and fix up to 30 GitHub issues per run. Bounded batching with staged validation ensures controlled change management and prevents accidental breakage across the release branch.

Why does my bug fix workflow require a separate git worktree for each issue?

A separate git worktree per issue isolates bug fixes on dedicated fix branches. This prevents cross-contamination of changes, ensures safe regression test generation, and maintains strict branch lifecycle rules before merging.