issue-validator

Evaluate GitHub issues for implementability and output a structured JSON report.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/pcortes/swarm-attack --skill issue-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-validator
Source: https://github.com/pcortes/swarm-attack/tree/main/default-skills/issue-validator
Command: npx skills add https://github.com/pcortes/swarm-attack --skill issue-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automatically reviews generated GitHub issues to ensure they are clear, complete, and implementable. It prevents developers from starting work on poorly defined tasks, reducing rework, clarifying scope, and improving overall project efficiency and developer satisfaction.

Core Features & Use Cases

  • Automated Issue Quality Check: Evaluates issue titles, descriptions, acceptance criteria, and scope for clarity and completeness.
  • Problem Identification: Flags issues that are too broad, lack sufficient detail, have ambiguous requirements, or miss error handling specifications.
  • Pre-Development Assurance: Ensures tasks are truly ready for development, minimizing mid-sprint clarifications and delays.
  • Use Case: After issues are generated for a new feature, this Skill reviews them, identifies an issue titled "Add authentication" as too broad and lacking detail, and recommends breaking it down into smaller, more specific tasks with clear acceptance criteria.

Quick Start

Validate the list of generated GitHub issues provided in the attached JSON file 'issues.json' for completeness, clarity, and implementability.

Frequently Asked Questions about issue-validator

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

FAQPage Schema
How do I validate GitHub issues for clarity before development starts?

Issue validation evaluates GitHub issue titles, descriptions, acceptance criteria, and scope for clarity and completeness. It identifies ambiguous requirements, overly broad tasks, and missing technical details, ensuring tasks are implementable before developers begin work and reducing mid-sprint rework.

What makes a GitHub issue ready for implementation?

A ready issue has a specific title, detailed description with context, clear acceptance criteria, defined scope boundaries, and relevant technical specifications. Issue validation checks for these elements and flags issues that lack specificity, error handling details, or sufficient breakdown for actionable work.

Can I automate quality checks on issues during backlog grooming?

Yes. Issue validation runs automated quality checks on issue batches during backlog grooming, refinement, or new feature planning. It produces structured JSON reports identifying completeness gaps and implementability risks, enabling teams to remediate issues before sprint commitment.

How do I identify issues that are too broad or ambiguous?

Issue validation flags tasks with vague requirements, unclear scope, insufficient acceptance criteria, or missing technical context. It detects overly broad issues like 'Add authentication' and recommends breaking them into smaller, specific tasks with measurable acceptance criteria.

What output do I get from issue validation?

Issue validation produces a structured JSON report containing an issues_reviewed array with per-issue assessment results and an overall_assessment summary. Each entry identifies clarity gaps, scope issues, missing details, and completeness status for quality assurance and project planning.

Does issue validation work with generated or manually created issues?

Issue validation applies to any GitHub issue data—generated or manual—that includes title, description, acceptance criteria, scope, and technical context. It evaluates completeness and implementability regardless of origin, supporting quality assurance in new feature planning and task refinement workflows.