review-test

Audit tests for changed code and identify coverage gaps across JavaScript, TypeScript, Python, Go, and Rust.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/0xdeafcafe/skills --skill review-test-0xdeafcafe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-test
Source: https://github.com/0xdeafcafe/skills/tree/main/skills/review-test
Command: npx skills add https://github.com/0xdeafcafe/skills --skill review-test-0xdeafcafe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you assess whether tests on changed code are actually effective, not just present. It audits touched files to find weak assertions, missing coverage on new branches, brittle mocks, flaky failures, poor test levels, and other issues that let bugs slip through despite a passing test suite.

Core Features & Use Cases

  • Read-only test audit: Reviews changed source files and their associated tests without modifying code or test files.
  • Quality-focused findings: Flags assertion problems, mock misuse, level mismatches, test independence issues, snapshot churn, and uncovered new code paths.
  • Scoped execution: Uses PR diff, working tree changes, or an explicit file list to target only relevant tests and runs them with the repository's existing test tooling.
  • Structured output: Emits prioritized findings in a consistent finding schema so another workflow can fix them later.
  • Use Case: Before opening or approving a PR, use this Skill to check whether newly added logic and edge cases are meaningfully tested and whether the changed tests would fail for the right reasons.

Quick Start

Ask the agent to review the tests for the current PR and report only test-quality findings.

Frequently Asked Questions about review-test

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

FAQPage Schema
How do I check if my tests actually cover new code changes in a pull request?

Test quality audits check if tests effectively cover changed code by running scoped test suites and analyzing coverage to identify gaps that would let regressions pass unnoticed. This ensures newly added logic is meaningfully tested before merging.

Can I audit test quality for repositories using Python, Go, or Rust?

Yes, test quality audits support JavaScript, TypeScript, Python, Go, and Rust repositories. The audit uses the project's existing test runner and diff context to execute relevant tests and detect assertion or coverage issues across these languages.

What types of test quality issues can be detected in changed code?

Test quality audits detect weak assertions, missing coverage on new branches, brittle mocks, flaky failures, test isolation problems, snapshot churn, and poor test levels that allow bugs to slip through despite a passing test suite.

How do I find weak assertions and mock misuse before merging a GitHub pull request?

Run a read-only test audit on your PR diff to flag assertion problems, mock misuse, and uncovered new code paths. The audit emits prioritized findings in a structured schema so another workflow can fix them later.

Does the test review process modify my source code or test files?

No, test quality audits perform read-only analysis of touched source and test files. They execute scoped test suites and coverage checks without modifying your code, ensuring your repository remains unchanged during the review process.

What is the best way to automate test quality checks for regression testing?

Automate test quality checks by scoping audits to PR diffs, working tree changes, or explicit file lists. The audit executes targeted tests, detects isolation and coverage issues, and outputs structured findings for automated regression prevention.