spec-reviewer

Review speckit spec.md and plan.md files in GitHub PRs for structural issues.

1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/tjespers/claude-skills --skill spec-reviewer-tjespers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-reviewer
Source: https://github.com/tjespers/claude-skills/tree/main/spec-reviewer
Command: npx skills add https://github.com/tjespers/claude-skills --skill spec-reviewer-tjespers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, curl, jq, openssl, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Automates the review of speckit specification and planning documents in GitHub PRs, identifying structural issues, inconsistencies, cross-reference errors, and quality gaps to accelerate reviews.

Core Features & Use Cases

  • Analyze PR diffs to locate spec.md and plan.md and surface issues.
  • Validate cross-document consistency and alignment with plan/checklists.
  • Post a structured GitHub review with inline comments to guide authors.

Quick Start

Activate the spec-reviewer on a PR containing spec/plan documents to generate an inline, structured review.

Frequently Asked Questions about spec-reviewer

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

FAQPage Schema
How do I automate spec review for PRs containing speckit documents?

To automate spec review for PRs, this skill analyzes GitHub PR diffs to locate spec.md and plan.md files, surfacing structural issues, inconsistencies, and cross-reference errors. It validates cross-document alignment and posts structured inline comments directly on the PR to guide authors.

What does automated plan and spec checklist validation check for in a GitHub PR?

Automated spec and plan checklist validation checks for required document sections, ensures alignment with the plan, flags functional requirement and specification gaps, and identifies cross-document contradictions between spec.md and plan.md files to accelerate reviews.

Do I need a GitHub App to post inline PR review comments?

Yes, you need a GitHub App or AUTH flow configured to post structured inline PR review comments and preserve provenance. The automation relies on this authentication mechanism to interact with GitHub PRs.

What dependencies are required for automated GitHub PR spec validation?

Automated GitHub PR spec validation requires gh, curl, jq, and openssl installed in your environment. These dependencies handle GitHub API interactions, data parsing, and authentication flows for the automated review process.

Can I validate cross-document consistency between spec and plan files?

Yes, you can validate cross-document consistency between spec and plan files. The automation ensures alignment with plan checklists and flags contradictions or gaps between functional requirements in spec.md and plan.md documents during the PR review.