test

Identify untested branches, error paths, and boundary conditions in test suites.

7|Updated May 28, 2026

Search Tags:#testing #completeness #review #code-quality #edge-cases #test-coverage

Ready to run

npx skills add https://github.com/zcaceres/skills --skill test-zcaceres

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test
Source: https://github.com/zcaceres/skills/tree/main/skills/test
Command: npx skills add https://github.com/zcaceres/skills --skill test-zcaceres

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the gap between superficial line coverage and true behavioral completeness by identifying missing edge cases, error paths, and boundary conditions in your test suite.

Core Features & Use Cases

Behavioral Gap Analysis: Cross-references source code against existing tests to find untested branches and error paths.
Dispatcher Architecture: Supports extensible subcommands for future test-related tasks like generation and pruning.
Use Case: Use this when you want to ensure your code is robust against edge cases, such as empty inputs, boundary overflows, or specific error conditions that your current tests might be ignoring.

Quick Start

Ask the agent to review the test coverage for the current branch by typing test gaps.

Frequently Asked Questions about test

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

FAQPage Schema

How do I find missing edge cases and error paths in my test suite?▼

Find missing edge cases by cross-referencing source code logic against existing test assertions to detect untested branches, error paths, and boundary conditions. This structural code analysis reveals behavioral gaps that superficial line coverage misses.

What is the best way to audit test coverage for behavioral completeness?▼

Auditing test coverage for behavioral completeness involves analyzing source code against test assertions to identify untested boundary conditions and error paths. It scopes analysis to git diffs or specific file paths to ensure code robustness.

Can I analyze test gaps for a specific git diff or file path?▼

Yes, you can analyze test gaps for a specific git diff or file path. The analysis scopes structural code verification to the provided repository source and test files, detecting untested branches within the targeted changes.

How do I check if my tests cover boundary conditions and empty inputs?▼

Check boundary condition coverage by performing behavioral verification against source logic. The analysis identifies missing tests for empty inputs, boundary overflows, and specific error conditions that current assertions might be ignoring.

Do I need repository source files to perform structural code analysis for test gaps?▼

Yes, you need access to repository source and test files to perform structural code analysis. The behavioral gap analysis requires cross-referencing actual code logic against existing test assertions to detect untested branches.

Why does high line coverage still miss untested branches and error paths?▼

High line coverage misses untested branches because it measures execution frequency rather than behavioral completeness. Cross-referencing source logic against test assertions identifies specific error paths and boundary conditions that line metrics ignore.