issue-verifier

Verify GitHub issue goal alignment, acceptance coverage, and durability before closure.

289|39|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/kxn/codex-remote-feishu --skill issue-verifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-verifier
Source: https://github.com/kxn/codex-remote-feishu/tree/main/.codex/skills/issue-verifier
Command: npx skills add https://github.com/kxn/codex-remote-feishu --skill issue-verifier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Independent, read-only verification of nearly finished GitHub issues before closure is performed to ensure alignment with goals and acceptance criteria.

Core Features & Use Cases

  • Performs an independent review of issue body, maintainer/user comments, linked design/docs, and changed files to validate intent and scope.
  • Produces a formal verdict with explicit acceptance gaps and actionable next steps, preventing premature close.
  • Provides guardrails to hand control back to contributor or issue workflow when additional work is needed.

Quick Start

Provide the GitHub issue URL or number and I will run an independent read-only verification pass before close.

Frequently Asked Questions about issue-verifier

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

FAQPage Schema
How do I verify a GitHub issue before closing it?

You can verify a GitHub issue before closing by performing an independent, read-only review of the issue body, comments, linked docs, and changed files to validate goal alignment and acceptance coverage. This produces a structured checklist verdict with actionable gaps and recommendations.

What is independent issue verification for acceptance criteria?

Independent issue verification is a read-only process that validates whether a nearly finished GitHub issue meets its original goals and acceptance criteria. It reviews issue bodies, comments, linked docs, and diffs to produce a formal verdict preventing premature closure.

How do I check if an issue covers all acceptance criteria from comments and diffs?

You can check acceptance coverage by applying independent validation across the issue body, maintainer and user comments, linked design documents, and changed files. This identifies explicit acceptance gaps and generates actionable next steps before the issue closes.

Does issue verification execute code changes to fix gaps it finds?

Issue verification does not execute code changes by default. It performs a read-only validation pass and provides guardrails to hand control back to the contributor or issue workflow when additional work is needed to meet acceptance criteria.

When should I run an independent verification pass on a GitHub issue?

You should run an independent verification pass on a GitHub issue when it is nearly finished and ready for closure. This ensures durability and intent alignment across the issue scope before finalizing, preventing premature closure due to missed acceptance gaps.