issue-check

Review GitHub issue markdown files for implementation-readiness and gaps.

29|4|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/matsen/bipartite --skill issue-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-check
Source: https://github.com/matsen/bipartite/tree/main/skills/issue-check
Command: npx skills add https://github.com/matsen/bipartite --skill issue-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review a GitHub issue markdown file for implementation-readiness, fix gaps, then submit via /issue-file.

Core Features & Use Cases

  • Load the issue markdown and verify required sections (title, description, acceptance criteria) exist.
  • Check for constitution alignment (MUST/SHOULD) and DESIGN.md references if present, flag violations for remediation.
  • Detect missing prerequisites, placeholders, and provide concrete fixes before submission.
  • Support end-to-end flow by enabling the /issue-file submission once gaps are resolved.

Quick Start

Run /issue-check ISSUE-feature-name.md to initiate the automated review.

Frequently Asked Questions about issue-check

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

FAQPage Schema
How do I check if a GitHub issue is ready for implementation before submission?

To check if a GitHub issue is implementation-ready, you can automate the review of issue markdown files to verify required sections like title, description, and acceptance criteria exist. This ensures completeness and identifies gaps before submission.

How do I automate issue review to align with project constitution and design documents?

You can automate issue review to enforce constitution alignment by checking issue markdown against CONSTITUTION.md and DESIGN.md files. The process flags violations of MUST and SHOULD principles and detects missing prerequisites or placeholders for remediation.

Do I need CONSTITUTION.md and DESIGN.md files to review GitHub issues for implementation-readiness?

You do not strictly need CONSTITUTION.md and DESIGN.md files to run an issue review, but if provided, the automated check will validate referenced documents and flag violations against defined MUST and SHOULD principles.

What is the best way to resolve placeholders and gaps in GitHub issue markdown files?

The best way to resolve placeholders and gaps in GitHub issue markdown files is to run an automated issue review that detects missing prerequisites and provides concrete fixes, ensuring the issue is complete and implementation-ready.

Why does my GitHub issue fail the conformance check during automated review?

A GitHub issue fails the conformance check during automated review if it lacks required sections, violates MUST or SHOULD principles defined in the CONSTITUTION.md, contains unresolved placeholders, or misses referenced DESIGN.md documents.

Can I submit a GitHub issue automatically after fixing the gaps found during the markdown review?

Yes, you can submit a GitHub issue after fixing gaps by using the /issue-file command. This command is enabled once the automated issue review resolves all missing prerequisites, placeholders, and conformance violations.