Engineering / Testing Quality

Test Gap Analyzer

Identify missing unit, integration, regression, and edge-case test scenarios for recently changed code.

DocumentationAgent instructionsRequirements & limits

Use when changed code needs missing unit, integration, regression, and edge-case scenarios identified.

Inputs

  • changed files or diff summary
  • current tests covering those files
  • known product edge cases or failure reports

Outputs

  • Missing test scenarios
  • Risk ranking
  • Suggested next tests

Before you begin

  • Reading and copying the procedure require no terminal setup. Check requirements for any packaged programs separately.

Try this first

Read the procedure and supply its documented inputs. Use the full text in an agent app or chat that supports pasted instructions, following that host's guidance.

Limits for this step
  • Instruction package only; it does not provide or authorize an executable runtime capability.
  • Safe for inspection and recommendation; require human approval before broadening test scope or changing suites.
Read full instructionsHide full instructionsSKILL.md · v0.1.0

Test Gap Analyzer

When to use

  • Use after a code change when you want to know what tests are still missing.
  • Use during PR review to assess test completeness.
  • Use when failures hint at an untested edge case.

Inputs required

  • changed files or diff summary
  • current tests covering those files
  • known product edge cases or failure reports

Workflow

  1. Inspect changed code paths and existing tests.
  2. Map missing coverage by scenario type: unit, integration, regression, negative path, and edge case.
  3. Assess assertion quality and setup realism.
  4. Prioritize missing tests by defect risk.
  5. Suggest next tests in a deterministic structure.

Output format

  • Coverage Summary
  • Missing Scenarios
  • Weak Assertions
  • Highest-Risk Gaps
  • Recommended Next Tests

Guardrails

  • Do not invent coverage data that was not observed.
  • Separate code-risk analysis from measured test coverage.
  • Tie each suggested scenario to specific code behavior.
  • Escalate if no tests are available to inspect.

Failure modes

  • If tests are absent, label the change as high-risk.
  • If fixtures are incomplete, call out the exact missing setup.
  • If code behavior is ambiguous, mark confidence as low.
View file metadata
---
name: test-gap-analyzer
description: Review changed code and current tests to identify missing
  scenarios, weak assertions, and regression blind spots.
---

Summary sources · Catalogue metadata, skill.yaml, SKILL.md, examples/input.json, examples/output.json · v0.1.0 · Release package

Install instruction files

These commands copy guidance into the selected runtime directories. Confirm that your agent app discovers it. Any packaged programs need separate setup and verification.

Install (Codex)

./bin/skills-hub install engineering/[email protected] --runtime codex

Install (Claude)

./bin/skills-hub install engineering/[email protected] --runtime claude

Install (Generic)

./bin/skills-hub install engineering/[email protected] --runtime generic --target ./my-agent/skills

How You Can Use This

Documentation

Resource form: Agent instructions

Read or copy the guidance. Any packaged programs have separate execution requirements and evidence.

First run: Read SKILL.md and follow the documented workflow.

Current limits

  • Instruction package only; it does not provide or authorize an executable runtime capability.
What installation and verification mean
File installation
Places package files and generated configuration in the selected directories.
Native discovery
Your agent app finds and accepts the instructions, tools or plugin registrations.
Mock execution
Exercises sample fixtures. Connected data and provider effects need a separate check.
Connected operation
Requires current configuration, provider authentication, scoped permissions and a successful operation in your intended environment.

Declared compatibility

Compatibility unknown: versions and capabilities have not been declared.

Classification: declared

Technical details and release files

Operational Summary

Execution mode: read-only-local-inspection

Approval boundary: Safe for inspection and recommendation; require human approval before broadening test scope or changing suites.

Review and lifecycle

Review maturity: Experimental

Security review declaration: Not declared

Lifecycle: Active

These release declarations are separate from evidence that a workflow operates in your environment.

Runtime & Dependencies

ID: engineering/test-gap-analyzer

Tags: tests, gaps, regression, quality

Runtimes: codex, claude, generic

Tool dependencies: 0

API dependencies: 0

Dependencies

Tools: Not documented

APIs: Not documented

Outputs

  • Missing test scenarios
  • Risk ranking
  • Suggested next tests