review-testing

Analyze code scope for test gaps, coverage, quality, and maintainability.

7|3|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/nesnilnehc/ai-cortex --skill review-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-testing
Source: https://github.com/nesnilnehc/ai-cortex/tree/main/skills/review-testing
Command: npx skills add https://github.com/nesnilnehc/ai-cortex --skill review-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams audit code for testing concerns by evaluating the presence of tests, coverage adequacy, test quality and structure, handling of edge cases, and maintainability within a given code scope.

Core Features & Use Cases

  • Test existence checks: identify modules or components that lack tests.
  • Coverage assessment: evaluate whether high-risk paths and critical functionality are tested.
  • Quality and structure evaluation: assess test organization, meaningful assertions, and behavior over implementation details.
  • Test types and layering: analyze unit, integration, and end-to-end coverage distribution.
  • Edge cases and error paths: ensure boundary conditions and failure modes are tested.
  • Maintainability: ensure tests are DRY, well-named, and robust against refactors.

Quick Start

Provide a findings list for the given code scope focusing on testing concerns.

Frequently Asked Questions about review-testing

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

FAQPage Schema
How do I audit code for test coverage and quality without executing tests?

Yes, you can statically assess test coverage by analyzing a provided code scope to identify gaps in high-risk paths, critical functionality, and boundary conditions, outputting structured findings without executing any runtime tests.

What is a cognitive test review for pre-release or refactor onboarding?

A cognitive test review statically analyzes a given code scope to evaluate test existence, coverage adequacy, and maintainability, producing a findings list with location, category, severity, and suggestions without executing runtime tests.

How do I check if my unit, integration, and end-to-end tests have adequate coverage?

Evaluate test layering by analyzing the distribution of unit, integration, and end-to-end coverage within a code scope to identify gaps in critical functionality and high-risk paths, generating a structured findings list with severity and suggestions.

Does this test analysis approach work for checking edge cases and error paths?

The analysis evaluates edge cases and error paths by checking the code scope for boundary conditions and failure modes, generating a standardized findings list that identifies missing coverage along with severity and actionable suggestions.

What are the limitations of static test quality analysis without runtime execution?

Since this approach requires no runtime test execution, it cannot verify actual pass or fail states, limiting its scope to statically evaluating test existence, coverage adequacy, edge cases, and maintainability within the supplied code scope.