reviewing-tests

Identify evidence gaps in cross-language unit and integration test suites.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/outcomeeng/claude --skill reviewing-tests-outcomeeng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-tests
Source: https://github.com/outcomeeng/claude/tree/main/plugins/test/skills/reviewing-tests
Command: npx skills add https://github.com/outcomeeng/claude --skill reviewing-tests-outcomeeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Foundational test review methodology to ensure that assertions are truly evidenced by tests and to reject gaps that could let CI pass falsely.

Core Features & Use Cases

  • Provides a four-phase review protocol (spec structure validation, evidentiary integrity, lower-level assumptions, and ADR/PDR compliance) to rigorously verify test coverage.
  • Supports language-specific extensions (reviewing-python-tests, reviewing-typescript-tests) to enforce consistent standards across stacks.
  • Enables auditors to identify adversarial gaps, silent skips, or misaligned test strategies, and to generate concrete rejection guidance.

Quick Start

Run the reviewing-tests workflow on your test suite to detect evidence gaps and reject any assertion that is not fully supported.

Frequently Asked Questions about reviewing-tests

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

FAQPage Schema
How do I verify test assertions are actually evidenced in my CI pipeline?

Verify test assertions by applying a four-phase review protocol that validates spec structure, evidentiary integrity, lower-level assumptions, and ADR/PDR compliance to detect evidence gaps and reject falsely passing tests.

What is an adversarial test check and when do I need it for unit and integration tests?

An adversarial test check identifies silent skips, misaligned testing strategies, and assertion gaps in unit and integration tests. You need it to ensure your CI pipeline does not pass falsely due to unvalidated or weakly linked test evidence.

How do I review test suites to enforce typed assertion formats and inline file linkage?

Review test suites by running a protocol that enforces typed assertion formats and verifies inline or test file linkage. This evidentiary integrity phase ensures every assertion is directly supported by concrete test logic.

Can I use this test review methodology across different programming language stacks?

Yes, you can use this foundational test review methodology across stacks. It supports language-specific extensions for Python and TypeScript tests to enforce consistent evidentiary standards and typed assertion formats across varied CI environments.

What's the best way to identify silent skips and misaligned testing strategies in CI?

The best way to identify silent skips and misaligned strategies is to execute a rigorous test coverage review that checks for adversarial gaps and enforces proper level testing, generating concrete rejection guidance for unsupported assertions.

Does reviewing tests require spec-driven reviews and ADR compliance to work?

Yes, reviewing tests requires spec-driven reviews and ADR/PDR compliance to validate foundational assumptions. The protocol checks lower-level assumptions and architectural decision records to ensure tests align with intended design specifications.