← ClaudeAtlas

issue-resolution-reviewerlisted

Audits closed GitHub issues to verify whether root causes were genuinely resolved, if follow-on execution friction appeared, or if systemic improvements were retained. Trigger with "audit closed issues", "review issue resolution quality", "was this issue actually fixed", or as a post-closure quality gate on issues labeled resolution:fixed or resolution:superseded. Migrated from the former issue-resolution-reviewer agent (2026-09-05): deterministic audit against fixed criteria, no interview, no code writes — fits the skill archetype, not the agent archetype.
richfrem/agent-plugins-skills · ★ 6 · Code & Development · score 74
Install: claude install-skill richfrem/agent-plugins-skills
<example> <commentary>User wants a post-closure quality audit on resolved issues.</commentary> user: "Audit the issues we closed last week — did the fixes actually stick?" assistant: Lists closed issues with resolution:fixed/resolution:superseded, checks recent test runs and friction logs for each, and reports which are confirmed-resolved vs. which show recurring friction. </example> ## Dependencies This skill requires **Python 3.8+** and standard library only, plus the `gh` CLI (GitHub CLI) authenticated for this repository. --- # Issue Resolution Reviewer Performs post-closure quality audits on resolved repository issues labeled `resolution:fixed` or `resolution:superseded`. This is a read-only report generator — it never mutates issue state or repository files on its own. ## Execution Flow ### Phase 1: Collect Closed, Resolved Issues ```bash gh issue list --state closed --label "resolution:fixed" --json number,title,closedAt,labels gh issue list --state closed --label "resolution:superseded" --json number,title,closedAt,labels ``` ### Phase 2: Verify Root Cause & Regression State For each issue: 1. Read the issue body and closing comment for the stated root cause and fix commit/PR. 2. Check recent test runs, CI logs, and `references/map-debt.md` for any friction event referencing the same file/component logged **after** the issue's `closedAt` date. 3. Classify each issue: `CONFIRMED_RESOLVED`, `RECURRING_FRICTION`, or `INCONCLUSIVE` (insufficient evidence e