find-missing-tests

Detect untested code and generate GitHub issues with acceptance criteria.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/stevengonsalvez/nanoclaw-standalone --skill find-missing-tests-stevengonsalvez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-missing-tests
Source: https://github.com/stevengonsalvez/nanoclaw-standalone/tree/main/container/skills/find-missing-tests
Command: npx skills add https://github.com/stevengonsalvez/nanoclaw-standalone --skill find-missing-tests-stevengonsalvez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze codebases to identify missing test coverage and automatically propose GitHub issues to track gaps.

Core Features & Use Cases

  • Automated gap detection: Scans the repository for untested functions, classes, and modules, including edge cases.
  • Issue generation: Creates detailed GitHub issues with clear titles, references to code locations, and acceptance criteria.
  • Progress reporting: Generates a summary of coverage gaps and tracks resolved gaps over time.

Quick Start

Point the skill at a repository and request it to identify missing tests and create GitHub issues.

Frequently Asked Questions about find-missing-tests

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

FAQPage Schema
How do I identify missing test coverage in my codebase?

Code coverage gap detection works by scanning the repository to locate untested functions, classes, modules, and edge cases across unit, integration, and regression areas. It analyzes the codebase to find coverage gaps and optionally synthesizes a summary report.

Can I automatically create GitHub issues for missing tests?

Yes, you can automatically create GitHub issues for missing tests. The skill generates detailed issue metadata including titles, referenced files and lines, acceptance criteria, labels, and recommended test types to track coverage gaps.

How do I scan specific files for missing tests instead of the whole repository?

To scan specific files for missing tests, provide the target files or directories in the ARGUMENTS when running the skill. If no arguments are provided, it defaults to scanning the entire repository for coverage gaps.

What information is included in the generated GitHub issues for code coverage?

Generated GitHub issues for code coverage include detailed metadata such as clear titles, references to specific files and lines, acceptance criteria, labels, and recommended test types to ensure gaps are actionable.

Does this test gap detection tool work without external dependencies?

Yes, this test gap detection tool works without external dependencies. It operates directly on your repository to analyze untested functions and generate GitHub issues without requiring additional components.