scan-coverage

Identify source files without corresponding tests in packages/ and apps/ directories.

Updated Aug 27, 2026

Search Tags:#automation #deduplication #ci #test-coverage #missing-tests #issues.md

Ready to run

npx skills add https://github.com/TrevorPLam/agency --skill scan-coverage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scan-coverage
Source: https://github.com/TrevorPLam/agency/tree/main/.windsurf/skills/scan-coverage
Command: npx skills add https://github.com/TrevorPLam/agency --skill scan-coverage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects missing tests to improve software reliability and ensure code changes are properly validated.

Core Features & Use Cases

Automated scanning: traverses repo to identify source files without corresponding tests.
Deduplication and tracking: creates unique issues for new findings and avoids duplicates.
Integrations: writes results to tasks/issues.md for downstream triage and workflow automation.

Quick Start

Run the scan across packages/ and apps/ within 30 seconds and paste the full output.

Frequently Asked Questions about scan-coverage

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

FAQPage Schema

How do I identify missing tests in a multi-package repository?▼

To identify missing tests in a multi-package repository, scan the packages/ and apps/ directories to flag source files without corresponding tests. This automated scanning process assesses test coverage gaps to improve software reliability.

How does test coverage deduplication work for CI workflows?▼

Test coverage deduplication works by computing content hashes for findings during the scan. This creates unique issues for new missing test files and avoids duplicates, producing a clean summary suitable for issue tracking in your CI workflows.

Can I use automated scanning to flag missing tests during local development?▼

Yes, you can use automated scanning to flag missing tests during local development. The scan applies across packages/ and apps/ directories locally, enforcing a 30-second timeout to quickly identify source files without corresponding tests.

What's the best way to track missing test coverage gaps for issue triage?▼

The best way to track missing test coverage gaps is writing deduplicated results to tasks/issues.md. This output format enables downstream triage and workflow automation by maintaining a tracked list of source files lacking tests.

Why does my test coverage scan time out before finishing?▼

A test coverage scan times out to enforce a strict 30-second execution limit across packages/ and apps/ directories. This timeout threshold ensures the automated scanning process remains efficient for CI workflows and local development.

Do I need specific dependencies to scan for missing tests?▼

No, you do not need specific dependencies to scan for missing tests. The automated scanning operates directly on your repository structure to flag files without corresponding tests and write deduplicated results to tasks/issues.md.