New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Review Spec

by Terry-Mao in Terry-Mao/AICodingFlow

Review a spec-only GitHub pull request from pinned prdiff.txt and prdescription.txt snapshots, then write and validate review.json with document-quality findings.

MITAuto-check passedDevelopment

Install Review Spec

skills CLI
$ npx skills add Terry-Mao/AICodingFlow --skill review-spec -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Terry-Mao/AICodingFlow review-spec --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Terry-Mao/AICodingFlow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/review-spec .claude/skills/review-spec && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
review-spec
GitHub stars
167
Token cost
~1.1k tokens
SKILL.md length
552 words
Files
1
Skills in repo
30
Repo updated
First seen
Licence
MIT

At a glance

Review a spec-only GitHub pull request from pinned prdiff.txt and prdescription.txt snapshots, then write and validate review.json with document-quality findings.

  • Works in 11 steps: Read .agents/contracts/review.md. → Read pr_description.txt. → Read review_discussion_context.json when… → …
  • Tasks that involve Pull requests
  • SKILL.md covers Required Contract, Purpose, Applicability and Local Guidance, plus 2 more sections
  • Calls python3

What it does

Review Spec is an agent skill from Terry-Mao/AICodingFlow. Review a spec-only GitHub pull request from pinned prdiff.txt and prdescription.txt snapshots, then write and validate review.json with document-quality findings.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. It works with GitHub. The repository describes itself as: Setup a AI Coding Flow. The licence is MIT.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/review-spec”

Requirements

  • Python 3

Workflow steps

11 steps, taken from the first numbered list in SKILL.md.

  1. Read .agents/contracts/review.md.
  2. Read pr_description.txt.
  3. Read review_discussion_context.json when it exists and apply it only for
  4. Parse pr_diff.txt, build allowed changed-line targets, and collect changed
  5. Apply the specs/ scope guard from this skill.
  6. Read .github/skills/review-spec-repo/SKILL.md if present and apply only
  7. Read .github/skills/security-review-spec/SKILL.md and apply it as a
  8. Inspect repository files only when needed to evaluate whether the specs are
  9. Write one combined review.json with document-quality and supplemental
  10. Run python3 .github/skills/review-pr/scripts/validate_review_json.py pr_diff.txt review.json
  11. Fix review.json until validation passes.

What it can do on your machine

Read from SKILL.md and the folder at commit 7703e16. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Review Spec loads about 1.1k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 552 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~46
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Terry-Mao/AICodingFlow at commit 7703e16, republished under its MIT licence (© Terry-Mao). 552 words, ~1,128 tokens.

Download SKILL.mdSave it as .claude/skills/review-spec/SKILL.md (or your agent's skills folder).
name
review-spec
description
Review a spec-only GitHub pull request from pinned `pr_diff.txt` and `pr_description.txt` snapshots, then write and validate `review.json` with document-quality findings.

review-spec

Review one spec-only PR from stable local snapshot files and write the single output artifact review.json.

Required Contract

Read .agents/contracts/review.md first and follow it exactly. That contract is authoritative for snapshot trust, untrusted-input handling, PR_DIFF_V1 targeting, review.json structure, severity labels, suggestion blocks, validator requirements, and GitHub/API boundaries.

Do not run gh, post comments, regenerate snapshots, modify the spec files being reviewed, or modify files other than review.json.

Purpose

Use this skill for PRs whose changed files are all under specs/, including product specs, technical specs, design notes, plans, and similar planning documents. This skill reuses the shared review contract but changes the review lens from code defects to document quality.

Applicability

Before reviewing content, inspect the changed file paths in pr_diff.txt.

If every changed file is under specs/, perform a spec document review.

If any changed file is outside specs/:

  • Do not perform code-level review.
  • Write a valid review.json.
  • Put a top-level body note explaining that the PR is outside spec-only review scope and should use review-pr or be split.
  • Use comments: [] unless there is a spec-document finding that can still be safely attached to a changed specs/ line.

Local Guidance

After applying the shared contract, read .github/skills/review-spec-repo/SKILL.md when it exists and apply any non-conflicting repository-specific guidance.

Always read .github/skills/security-review-spec/SKILL.md and apply it as a non-conflicting supplemental design-level security pass on spec PRs. Fold any security findings into the same review.json; do not emit a separate output.

Review Focus

Prioritize findings that would materially affect implementation, review quality, or the ability to use the specs as source-of-truth planning documents:

  • Completeness: missing goals, non-goals, acceptance criteria, validation plans, edge cases, rollout notes, or open questions required by the issue or PR.
  • Clarity: ambiguous requirements, undefined terms, unclear state transitions, vague validation language, or requirements an implementation agent could reasonably misread.
  • Feasibility: plans that do not fit the current repository structure, permissions, automation boundaries, skill contracts, or validation workflow.
  • Alignment: scope drift, missing issue requirements, invented requirements, or product and technical specs that do not reflect the PR or issue intent.
  • Consistency: contradictions within a spec, between product and tech specs, or between examples, acceptance criteria, and validation steps.
Show full SKILL.md (194 more words)Show less

Only comment on formatting when it affects readability, executability, or a reviewer's ability to evaluate the spec. Do not request implementation changes; review whether the document describes the right behavior and a feasible plan.

For spec-only PRs, the workflow publishes both APPROVE and REJECT verdicts as GitHub COMMENT reviews. A REJECT verdict is machine-readable review state for the spec quality result; it does not become a GitHub blocking REQUEST_CHANGES review.

Workflow

  1. Read .agents/contracts/review.md.
  2. Read pr_description.txt.
  3. Read review_discussion_context.json when it exists and apply it only for duplicate suppression of prior bot review comments.
  4. Parse pr_diff.txt, build allowed changed-line targets, and collect changed file paths.
  5. Apply the specs/ scope guard from this skill.
  6. Read .github/skills/review-spec-repo/SKILL.md if present and apply only non-conflicting local guidance.
  7. Read .github/skills/security-review-spec/SKILL.md and apply it as a non-conflicting supplemental high-level security pass.
  8. Inspect repository files only when needed to evaluate whether the specs are complete, aligned, feasible, or consistent.
  9. Write one combined review.json with document-quality and supplemental security findings.
  10. Run python3 .github/skills/review-pr/scripts/validate_review_json.py pr_diff.txt review.json when running locally. In GitHub Actions, the workflow runs validation after Codex exits.
  11. Fix review.json until validation passes.

© Terry-Mao, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .github/skills/review-spec of Terry-Mao/AICodingFlow.

Open the folder on GitHubat commit 7703e16

Compare with similar skills

Review Spec next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Review Spec compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Review Spec this skillTerry-Mao/AICodingFlow167—~1.1kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from Terry-Mao/AICodingFlow

All 30 skills in this repo

  • PR Walkthrough

    Terry-Mao/AICodingFlow

    Generate a local static interactive D3 walkthrough of a pull request.

    167 GitHub stars~2.1k tokensUpdated 7 days ago
    Auto-check passed

  • Update PR Review

    Terry-Mao/AICodingFlow

    Improve repo-local PR review companion skills from human feedback on bot reviews.

    167 GitHub stars~1.1k tokensUpdated 7 days ago
    Auto-check passed

  • Implement Issue

    Terry-Mao/AICodingFlow

    Implement a GitHub issue in this repository by applying the local shared implement-specs workflow with repository-specific issue, spec-context, and summary-file handling.

    167 GitHub stars~2.3k tokensUpdated 7 days ago
    Auto-check passed

  • Implement Specs

    Terry-Mao/AICodingFlow

    Implement an approved feature from the repository's product and tech specs, keeping specs and code aligned in the same change as implementation evolves.

    167 GitHub stars~1.7k tokensUpdated 7 days ago
    Auto-check passed

  • Review PR

    Terry-Mao/AICodingFlow

    Review a GitHub pull request from pinned prdescription.txt, prdiff.txt, and optional speccontext.md snapshots, then write and validate review.json.

    167 GitHub stars~1k tokensUpdated 7 days ago
    Auto-check passed

  • Update Dedupe

    Terry-Mao/AICodingFlow

    Learn repo-local duplicate issue guidance from recent maintainer duplicate closures and propose updates to the dedupe companion skill.

    167 GitHub stars~1.1k tokensUpdated 7 days ago
    Auto-check passed

Works with

Categories

Questions about Review Spec

What does Review Spec do?

Review a spec-only GitHub pull request from pinned prdiff.txt and prdescription.txt snapshots, then write and validate review.json with document-quality findings. Review Spec is an agent skill from Terry-Mao/AICodingFlow.json with document-quality findings.

When should I use Review Spec?

Review Spec fits situations like: tasks that involve Pull requests.

How do I install Review Spec in Claude Code?

Run `npx skills add Terry-Mao/AICodingFlow --skill review-spec -a claude-code`. Or copy the skill folder (.github/skills/review-spec in Terry-Mao/AICodingFlow) into .claude/skills/review-spec in your project. Claude Code loads it when a task matches its description.

How do I install Review Spec in Codex?

Run `npx skills add Terry-Mao/AICodingFlow --skill review-spec -a codex`. Or copy the skill folder (.github/skills/review-spec in Terry-Mao/AICodingFlow) into .agents/skills/review-spec in your project. Codex loads it when a task matches its description.

Can I use Review Spec in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Terry-Mao/AICodingFlow --skill review-spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-spec, .gemini/skills/review-spec, .github/skills/review-spec and .opencode/skills/review-spec in your project.

What does Review Spec need to run?

Going by SKILL.md and its folder, Review Spec needs the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Review Spec access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Review Spec safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Review Spec use?

Review Spec is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Review Spec use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Review Spec?

Skills that share tags, products or a category with Review Spec: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Review Spec?

Terry-Mao (a GitHub user) maintains it in Terry-Mao/AICodingFlow, which has 167 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 3, 2026.

Source: Terry-Mao/AICodingFlow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.