skills.rest
csilost2001
csilost2001COMMUNITY
Explore all skills by this author →
GitHub

review-issue

Audit ISSUE implementation coverage by cross-checking related PRs against promised items.

Updated Apr 11, 2026
Search Tags:#audit#quality-assurance#code-review#pull-requests#issue-review#requirements-traceability#spec-consistency
One-click install
npx skills add https://github.com/csilost2001/html-designer --skill review-issue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-issue
Source: https://github.com/csilost2001/html-designer/tree/main/.claude/skills/review-issue
Command: npx skills add https://github.com/csilost2001/html-designer --skill review-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ISSUES outline implementation plans that must be reflected across multiple PRs. This Skill provides a structured audit to ensure every promise in an ISSUE is implemented by all related PRs, and tracks any changes or additions surfaced in ISSUE text or comments to maintain traceability and accountability.

Core Features & Use Cases

  • Cross-PR coverage verification: ensures all checklist items and acceptance criteria described in the ISSUE are implemented by merged PRs.
  • Change awareness: detects additions or modifications to the ISSUE text or comments and flags them for review.
  • Comprehensive reporting: generates a structured audit with must-fix and should-fix findings and a summary of merged PRs.
  • Spec/docs alignment: leverages any linked docs/spec references in the ISSUE to validate alignment between implementation and spec.

Quick Start

Open Claude Code and explicitly invoke /review-issue <ISSUE_NUMBER> after all related PRs are merged.

Frequently Asked Questions about review-issue

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

FAQPage Schema
How do I verify that all acceptance criteria in an issue are covered across multiple pull requests?▼

To verify acceptance criteria coverage across multiple pull requests, you can audit the issue by cross-checking all related merged PRs against the issue's promised checklist items and requirements to ensure full implementation before completion.

What's the best way to trace requirements consistency between issue specifications and merged code changes?▼

Tracing requirements consistency between issue specifications and merged code changes involves analyzing linked docs or spec references within the issue text and validating their alignment against the actual implementation in the merged pull requests.

How do I audit issue implementation coverage to find unmerged or missing deliverables?▼

Auditing issue implementation coverage involves cross-checking the issue's checklist items and later modifications against PR merge status, generating a structured report with must-fix and should-fix findings to highlight any missing deliverables.

Can I detect additions or modifications made in issue comments after PRs have already been merged?▼

Yes, detecting additions or modifications in issue comments after PRs are merged is possible by analyzing the issue text and comment history, which flags any surfaced changes to maintain traceability and accountability for later review.

Do I need all related pull requests to be merged before running an issue audit?▼

Yes, all related pull requests should be merged before running an issue audit, as the verification workflow cross-checks the issue's promised items against the PR merge status to output a comprehensive report of must-fix and should-fix findings.

What is cross-PR issue coverage verification and when do I need it?▼

Cross-PR issue coverage verification is a structured audit ensuring every promise in an issue is implemented by related PRs, needed when issues outline implementation plans with deliverables spread across multiple pull requests to maintain traceability.

Related Skills

Explore More Product & Management Skills→
2lab-ai2lab-ai
36

stv-verify

Compare issue acceptance criteria against GitHub PR changes to report gaps.

Official
Advanced
riccjohnriccjohn
1

technical-copywriter-review

Review technical writing and report issues by severity with suggested changes.

Community
Basic
blockblock
142

goosetown-researcher-github

Search GitHub repositories for issues, pull requests, code, and discussions using the gh CLI.

Official
Intermediate
letsur-devletsur-dev

git-commit-helper

Generate Spec-Kit-compliant git commit messages with Work Package references.

Official
Intermediate