issue-root-resolution

Audit and resolve issue clusters by verified root cause with evidence-gated closures.

6.1k|707|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/Gentleman-Programming/gentle-ai --skill issue-root-resolution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-root-resolution
Source: https://github.com/Gentleman-Programming/gentle-ai/tree/main/skills/issue-root-resolution
Command: npx skills add https://github.com/Gentleman-Programming/gentle-ai --skill issue-root-resolution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large defect backlogs accumulate duplicate, stale, and misclassified issues that waste maintainer time. This Skill audits issue clusters by verified root cause instead of surface symptoms, so fixes target the actual mechanism and closures are backed by evidence.

Core Features & Use Cases

  • Root-cause clustering: Partitions a defect backlog by causal mechanism rather than surface symptoms, recording counts in a meta-issue.
  • Read-only mechanism mapping: Produces file:line anchored maps of how code actually behaves today, flagging claim-vs-code mismatches before any fix is proposed.
  • Deletion-first fix ranking: Ranks solutions by what they remove, preferring mechanism deletion and static guards over new flags or verbs.
  • Evidence-gated closures: Closes issues only under four strict rules (fixed on main with commit and test, superseded by maintainer decision, surface removed, or duplicate of a fixed issue).
  • Use Case: Given 30 open bug reports on a repository, cluster them into 4 root causes, verify each against current main, propose deletion-shaped fixes, and close the stale ones with cited evidence.

Quick Start

Ask the agent to audit the open issue backlog, cluster the defects by root cause, and propose evidence-backed fixes and closures.

Frequently Asked Questions about issue-root-resolution

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

FAQPage Schema
How do I find the root cause of a cluster of bug reports?

Read full issue bodies and comments, then classify each report against the actual code or PR diff rather than titles. Cluster defects by causal mechanism and build a read-only mechanism map with one file:line anchor per claim before proposing any fix.

How to close stale GitHub issues with evidence?

Verify every fixed or broken claim against current main on the day you act, comparing report dates to fix merge dates. Close only under four rules: fixed on main with cited commit and test, superseded by maintainer decision, surface no longer exists, or duplicate of a fixed issue.

What is deletion-driven fix ranking for software defects?

It ranks solutions by what they remove: first deleting a mechanism so the defect class becomes impossible, then adding a static guard that fails tests on reintroduction, and only as a last resort adding new flags or mechanisms.

When should I not close an issue during a backlog audit?

Do not close when closure evidence is incomplete, when the blocker's fix lives in an unmerged PR, or when the failure mechanism cannot be verified on the latest build. List these as borderline with reasons instead of forcing a closure.

How does this differ from a single-defect workflow?

This Skill governs the cluster-level method: partitioning many issues by shared root cause, maintaining a meta-issue, and coordinating sliced implementation. A single-defect workflow handles one isolated bug from repro to fix.