review

Evaluate GitHub issue specs for gaps, ambiguities, and feasibility concerns.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill review-ryan-mahoney
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/ryan-mahoney/ryan-llm-skills/tree/main/skills/review
Command: npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill review-ryan-mahoney

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews GitHub issue specs for gaps, ambiguities, and viability, helping teams tighten scope before implementation.

Core Features & Use Cases

  • Gap/viability assessment of issue specs
  • Directly edit issues to reflect improved implementation details
  • Generate clear problem statements, goals, and acceptance criteria to guide development

Quick Start

Provide the GitHub issue number to have the AI review the spec, identify gaps, and propose edits if needed.

Frequently Asked Questions about review

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

FAQPage Schema
How do I identify gaps in a GitHub issue spec before implementation?

Tightening a GitHub issue involves evaluating the spec for gaps and viability concerns, then producing concrete edits to improve problem statements, goals, and acceptance criteria. These direct edits clarify requirements and guide subsequent implementation plans.

What is the best way to assess the feasibility of GitHub issues?

The best way to assess GitHub issue feasibility is to review the implementation plan and acceptance criteria for viability concerns. Analyzing these elements reveals ambiguities and scope issues, allowing you to apply concrete edits that tighten the spec.

Can I automatically generate acceptance criteria for GitHub issues?

Yes, you can generate clear acceptance criteria for GitHub issues by reviewing the existing spec for gaps and ambiguities. The analysis produces concrete suggestions and edits that establish clear goals and requirements to guide development.

Does reviewing an issue spec help fix unclear problem statements on GitHub?

Reviewing an issue spec helps fix unclear problem statements by analyzing the stated problem and goals to identify ambiguities. It produces concrete edits applied directly to the GitHub issue, clarifying requirements and guiding subsequent work.

When should I review GitHub issues for spec gaps and ambiguities?

You should review GitHub issues for spec gaps and ambiguities before implementation begins. Evaluating viability and analyzing acceptance criteria early prevents scope creep and ensures the planning details are tight enough to guide development.