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

Speckit Review Tests

by opsmill in opsmill/infrahub

Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.

Apache-2.0Auto-check passedTesting & QA

Install Speckit Review Tests

skills CLI
$ npx skills add opsmill/infrahub --skill speckit-review-tests -a claude-code

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

GitHub CLI
$ gh skill install opsmill/infrahub speckit-review-tests --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/opsmill/infrahub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/speckit-review-tests .claude/skills/speckit-review-tests && 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
speckit-review-tests
GitHub stars
533
Used in
1 other repo
Token cost
~1.2k tokens
SKILL.md length
637 words
Files
1
Skills in repo
32
Repo updated
First seen
Licence
Apache-2.0

At a glance

Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.

  • Works in 4 steps: Analyze Test Coverage Quality: Focus on… → Identify Critical Gaps: Look for → Evaluate Test Quality: Assess whether… → …
  • Tasks that involve Spec-driven development
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve Test coverage

What it does

Speckit Review Tests is an agent skill from opsmill/infrahub. Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires spec-kit project structure with .specify/ directory

It sits in Testing & QA, covering Spec-driven development and Test coverage. The repository describes itself as: Infrahub is a graph-based data management platform with built-in version control, CI workflows, peer review, and API access. It’s purpose-built to power reliable infrastructure… The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Spec-driven development
  • Tasks that involve Test coverage

Example prompts

  • “/speckit-review-tests”

Requirements

  • Compatibility (from SKILL.md): Requires spec-kit project structure with .specify/ directory

Workflow steps

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

  1. Analyze Test Coverage Quality: Focus on behavioral coverage rather than line coverage. Identify critical code paths, edge cases, and error…
  2. Identify Critical Gaps: Look for
  3. Evaluate Test Quality: Assess whether tests
  4. Prioritize Recommendations: For each suggested test or modification

What it can do on your machine

Read from SKILL.md and the folder at commit 2e1f1eb. 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

    No scripts in the folder and no shell commands in SKILL.md.

    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.

  • Compatibility

    Requires spec-kit project structure with .specify/ directory

    From compatibility in the SKILL.md frontmatter.

Context cost

Speckit Review Tests loads about 1.2k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 637 words of instructions outside code blocks.

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

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 opsmill/infrahub at commit 2e1f1eb, republished under its Apache-2.0 licence (© opsmill). 637 words, ~1,249 tokens.

Download SKILL.mdSave it as .claude/skills/speckit-review-tests/SKILL.md (or your agent's skills folder).
name
speckit-review-tests
description
Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.
compatibility
Requires spec-kit project structure with .specify/ directory
metadata.author
github-spec-kit
metadata.source
review:commands/tests.md

You are an expert test coverage analyst specializing in pull request review. Your primary responsibility is to ensure that PRs have adequate test coverage for critical functionality without being overly pedantic about 100% coverage.

Determine Changed Files:

If the user provided a file list or explicit instructions on how to retrieve files (e.g., only staged, only unstaged, a specific folder, etc.), follow those instructions directly.

Otherwise, you MUST execute the .specify/scripts/bash/detect-changed-files.sh with --json to detect changed files. Do not attempt to detect changes by running git commands directly, reading git state manually, or using any other method — always delegate to the script. The script automatically picks the best detection mode:

  • Mode A (feature branch): diffs the current branch against the default branch (main/master) from the merge-base, plus any staged and unstaged changes.
  • Mode B (working directory): falls back to staged + unstaged changes when there is no feature branch (e.g., working directly on the default branch).

JSON output: {"branch", "default_branch", "mode", "changed_files": [...]}

Note: The folder containing the script may be excluded from version control or hidden by search indexing. You must still locate and execute it — do not skip it or substitute your own file-detection logic.

Your Core Responsibilities:

  1. Analyze Test Coverage Quality: Focus on behavioral coverage rather than line coverage. Identify critical code paths, edge cases, and error conditions that must be tested to prevent regressions.

  2. Identify Critical Gaps: Look for:

    • Untested error handling paths that could cause silent failures
    • Missing edge case coverage for boundary conditions
    • Uncovered critical business logic branches
    • Absent negative test cases for validation logic
    • Missing tests for concurrent or async behavior where relevant

  3. Evaluate Test Quality: Assess whether tests:

    • Test behavior and contracts rather than implementation details
    • Would catch meaningful regressions from future code changes
    • Are resilient to reasonable refactoring
    • Follow DAMP principles (Descriptive and Meaningful Phrases) for clarity

  4. Prioritize Recommendations: For each suggested test or modification:

    • Provide specific examples of failures it would catch
    • Rate criticality from 1-10 (10 being absolutely essential)
    • Explain the specific regression or bug it prevents
    • Consider whether existing tests might already cover the scenario

Analysis Process:

  1. First, examine the PR's changes to understand new functionality and modifications
  2. Review the accompanying tests to map coverage to functionality
  3. Identify critical paths that could cause production issues if broken
  4. Check for tests that are too tightly coupled to implementation
  5. Look for missing negative cases and error scenarios
  6. Consider integration points and their test coverage
Show full SKILL.md (225 more words)Show less

Rating Guidelines:

  • 9-10: Critical functionality that could cause data loss, security issues, or system failures
  • 7-8: Important business logic that could cause user-facing errors
  • 5-6: Edge cases that could cause confusion or minor issues
  • 3-4: Nice-to-have coverage for completeness
  • 1-2: Minor improvements that are optional

Output Format:

Structure your analysis as:

  1. Summary: Brief overview of test coverage quality
  2. Critical Gaps (if any): Tests rated 8-10 that must be added
  3. Important Improvements (if any): Tests rated 5-7 that should be considered
  4. Test Quality Issues (if any): Tests that are brittle or overfit to implementation
  5. Positive Observations: What's well-tested and follows best practices

Important Considerations:

  • Focus on tests that prevent real bugs, not academic completeness
  • Consider the project's testing standards from project guidelines (typically in .specify/memory/constitution.md, CLAUDE.md, .github/copilot-instructions.md or equivalent) if available
  • Remember that some code paths may be covered by existing integration tests
  • Avoid suggesting tests for trivial getters/setters unless they contain logic
  • Consider the cost/benefit of each suggested test
  • Be specific about what each test should verify and why it matters
  • Note when tests are testing implementation rather than behavior

You are thorough but pragmatic, focusing on tests that provide real value in catching bugs and preventing regressions rather than achieving metrics. You understand that good tests are those that fail when behavior changes unexpectedly, not when implementation details change.

© opsmill, Apache-2.0. 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 .agents/skills/speckit-review-tests of opsmill/infrahub.

Open the folder on GitHubat commit 2e1f1eb

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in opsmill/infrahub, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Speckit Review Tests 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.

Speckit Review Tests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Speckit Review Tests this skillopsmill/infrahub5331 repos~1.2kAutomated safety check: PassApache-2.0
Evaluate PR Testsdotnet/maui23k—~2.9kAutomated safety check: PassMIT
Test Guidelinesgetsentry/sentry-dart873—~3.1kAutomated safety check: PassMIT
Evidence-First Development LoopAmazingAng/old-coder749—~5.4kAutomated safety check: NotesMIT
Testingdoorkeeper-gem/doorkeeper5.5k—~1.6kAutomated safety check: PassMIT
Reviewwebern/cargo-readme385—~2kAutomated safety check: NotesApache-2.0

Similar skills

  • Evaluate PR Tests

    dotnet/maui

    Official

    Reviews the tests added in a pull request for fix coverage, quality, edge cases and test type, and recommends lighter test types where they would do.

    23k GitHub stars~2.9k tokensUpdated today
    Testing & QAAuto-check passed

  • Test Guidelines

    getsentry/sentry-dart

    Official

    Enforce Sentry Dart/Flutter SDK test conventions for naming, structure, and fixtures.

    873 GitHub stars~3.1k tokensUpdated today
    Testing & QAAuto-check passed

  • Evidence-First Development Loop

    AmazingAng/old-coder

    Replaces line-by-line code review with an approved executable spec and a gauntlet of tests, types, coverage, and mutation checks the code must survive.

    749 GitHub stars~5.4k tokensUpdated 1 mo ago
    Testing & QAAuto-check: notes

  • Testing

    doorkeeper-gem/doorkeeper

    Write correct and complete RSpec tests for Doorkeeper. An agent skill from doorkeeper-gem/doorkeeper.

    5.5k GitHub stars~1.6k tokensUpdated 2 days ago
    Testing & QAAuto-check passed

  • Review

    webern/cargo-readme

    Reviews a GitHub pull request for correctness, architecture, security, backward compatibility, and test coverage.

    385 GitHub stars~2k tokensUpdated today
    Testing & QAAuto-check: notes

  • Supercov

    supercorp-ai/supercov

    Measures test coverage and code quality in a repository with the supercov CLI, and turns what it finds into small, focused tests or fixes.

    151 GitHub starsUsed in 1 repo~415 tokens
    Testing & QAAuto-check passed

More from opsmill/infrahub

All 32 skills in this repo

  • Analyzing CI Flakiness

    opsmill/infrahub

    Analyzes recent CI failures on pull requests to identify flaky tests, using retry outcomes (failed attempt → green re-run) and cross-PR recurrence as evidence, and maintains a local longitudinal…

    533 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Audit Docs

    opsmill/infrahub

    Audits internal (dev/) and external (docs/) documentation completeness for a feature, subject, or set of existing docs, maps changes indicated by the user, across Infrahub's documentation layers…

    533 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

  • Commit

    opsmill/infrahub

    Stages and commits the current changes onto a safe working branch, enforcing branch discipline and optionally pushing upstream.

    533 GitHub stars~2.8k tokensUpdated today
    Auto-check: notes

  • Creating Changelog Entries

    opsmill/infrahub

    A skill your agent uses when you've fixed a bug, added a feature, or made any user-facing change in a project that uses Towncrier and need to record it for the changelog — before committing or…

    533 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Creating Issues

    opsmill/infrahub

    Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue.

    533 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Creating Prd

    opsmill/infrahub

    Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue).

    533 GitHub stars~4k tokensUpdated today
    Auto-check passed

Categories

Questions about Speckit Review Tests

What does Speckit Review Tests do?

Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation. Speckit Review Tests is an agent skill from opsmill/infrahub. Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.

When should I use Speckit Review Tests?

Speckit Review Tests fits situations like: tasks that involve Spec-driven development; tasks that involve Test coverage.

How do I install Speckit Review Tests in Claude Code?

Run `npx skills add opsmill/infrahub --skill speckit-review-tests -a claude-code`. Or copy the skill folder (.agents/skills/speckit-review-tests in opsmill/infrahub) into .claude/skills/speckit-review-tests in your project. Claude Code loads it when a task matches its description.

How do I install Speckit Review Tests in Codex?

Run `npx skills add opsmill/infrahub --skill speckit-review-tests -a codex`. Or copy the skill folder (.agents/skills/speckit-review-tests in opsmill/infrahub) into .agents/skills/speckit-review-tests in your project. Codex loads it when a task matches its description.

Can I use Speckit Review Tests 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 opsmill/infrahub --skill speckit-review-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/speckit-review-tests, .gemini/skills/speckit-review-tests, .github/skills/speckit-review-tests and .opencode/skills/speckit-review-tests in your project.

What does Speckit Review Tests need to run?

SKILL.md names no scripts, command-line tools or credentials: Speckit Review Tests is instructions for the agent only. Compatibility (from SKILL.md): Requires spec-kit project structure with .specify/ directory.

Does Speckit Review Tests 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 Speckit Review Tests 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 Speckit Review Tests use?

Speckit Review Tests is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Speckit Review Tests use?

About 1.2k tokens (SKILL.md is roughly 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 Speckit Review Tests?

Skills that share tags, products or a category with Speckit Review Tests: Evaluate PR Tests (dotnet/maui, 23k stars), Test Guidelines (getsentry/sentry-dart, 873 stars), Evidence-First Development Loop (AmazingAng/old-coder, 749 stars) and Testing (doorkeeper-gem/doorkeeper, 5.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Speckit Review Tests?

opsmill (a GitHub organization) maintains it in opsmill/infrahub, which has 533 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on October 9, 2026.

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