skills.rest
SteveFeldman
SteveFeldmanCOMMUNITY
Explore all skills by this author →
Website𝕏@perfforensicsGitHub

find-missing-tests

Identifies missing test cases in files, directories, or PR diffs and outputs GitHub-issue-ready reports with prioritized suggestions.

5|Updated Mar 11, 2026
Search Tags:#testing#quality assurance#code review#code coverage#github issues#test cases
One-click install
npx skills add https://github.com/SteveFeldman/agents-skills --skill find-missing-tests
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: find-missing-tests
Source: https://github.com/SteveFeldman/agents-skills/tree/main/skills/find-missing-tests
Command: npx skills add https://github.com/SteveFeldman/agents-skills --skill find-missing-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the critical issue of inadequate test coverage by systematically identifying and reporting missing test cases for your codebase.

Core Features & Use Cases

  • Code Analysis: Analyzes specified files, directories, or PR diffs to understand code structure and logic.
  • Coverage Gap Identification: Compares existing test coverage against the target code to pinpoint untested paths, edge cases, and integration points.
  • Prioritized Reporting: Ranks missing tests by risk and importance, formatting them as actionable GitHub issues.
  • Use Case: A developer can use this skill to quickly assess the test coverage of a new feature or a refactored module, ensuring critical paths are not overlooked before deployment.

Quick Start

Use the find-missing-tests skill to review the file src/utils/helpers.ts and generate a list of missing tests.

Frequently Asked Questions about find-missing-tests

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

FAQPage Schema
How do I find missing test cases in my codebase?▼

To find missing test cases, you can analyze target files, directories, or PR diffs to map code logic. This process compares existing coverage against the code to pinpoint untested paths, edge cases, and integration points for prioritized reporting.

What is the best way to identify untested edge cases before deployment?▼

Identifying untested edge cases before deployment is best handled by reviewing code structure and logic. This approach compares existing test coverage against the target code to pinpoint untested paths and integration points, ranking them by risk.

Can I generate GitHub issues for untested code paths automatically?▼

Yes, you can generate GitHub issues for untested code paths automatically. By analyzing code to locate missing tests, the results are outputted as formatted GitHub issues complete with suggested test approaches and prioritized by importance.

How do I check test coverage gaps in a PR diff?▼

To check test coverage gaps in a PR diff, analyze the diff to understand the modified code structure. Comparing this against existing tests will pinpoint untested paths, edge cases, and integration points within the new changes.

Does this approach work for analyzing specific files and directories?▼

Yes, this approach works for analyzing specific files and directories. It reviews the specified target files or directories to understand code structure, mapping the logic to locate existing tests and identify missing test cases.

Related Skills

Explore More Software Engineering Skills→
ringlochidringlochid

coverage-review-gate

Identify missing or weak tests for code changes and PR reviews.

Community
Intermediate
MohamedSosa19MohamedSosa19

speckit-taskstoissues

Convert existing tasks into dependency-ordered GitHub issues.

Community
Intermediate
nearainearai
12.6k

qa-review

Review code changes for test coverage gaps, edge cases, and regression risks.

Official
Intermediate
mvillmowmvillmow
18

calculate-coverage

Calculate code coverage percentages and identify uncovered lines and branches.

Community
Intermediate