specimin-review

Analyzes GitHub pull requests against specification and generates structured review drafts.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/timsvoice/specimin --skill specimin-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specimin-review
Source: https://github.com/timsvoice/specimin/tree/main/.claude-plugin/skills/specimin-review
Command: npx skills add https://github.com/timsvoice/specimin --skill specimin-review

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Analyzes a PR against the feature specification, identifies gaps, and provides concrete feedback to speed up reviews and align changes with acceptance criteria.

Core Features & Use Cases

  • PR context aggregation: fetch diff summary, changed files, and spec/plan.
  • Gaps identification: highlight missing components, tests, or criteria.
  • Review artefact: save a structured review to the feature directory.

Quick Start

Run the review command on the current branch to generate a review notebook and save it locally.

Frequently Asked Questions about specimin-review

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

FAQPage Schema
How do I review a pull request against acceptance criteria?

PR review against acceptance criteria involves fetching the diff, reading the feature specification, and comparing changes to requirements. This Skill automates that process by analyzing PR changes, identifying gaps in implementation or testing, and generating a structured review document saved to your feature directory.

Can I automate code review feedback on GitHub pull requests?

Yes. This Skill uses GitHub CLI to fetch PR context, validates the diff against your specification, and produces actionable feedback highlighting missing components, tests, or criteria alignment—saving the review as a file for further action.

What information does a structured PR review need to include?

A structured PR review captures the diff summary, changed files, acceptance criteria from the spec, testing strategy, and gaps between what was implemented and what was required. This Skill generates that artifact by reading the feature directory and producing a review notebook.

Do I need GitHub CLI and jq to run PR reviews?

Yes. This Skill requires GitHub CLI (gh) to fetch PR data and jq to parse JSON responses. Both are dependencies you'll need installed before running the review command on your branch.

How does PR review fit into a feature workflow?

PR review follows feature specification and planning stages. It validates that changes match the spec and acceptance criteria, then outputs a review document. This structured feedback speeds up approval cycles and aligns implementation with requirements.

What happens if the PR or feature directory doesn't exist?

The Skill includes error handling that validates PR existence and the presence of a feature directory before processing. If either is missing, it fails gracefully rather than generating incomplete or incorrect feedback.