Skip to content
Back to skills

Specialist Test Gap Finder

ASecurity

Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.

  • 549 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added June 6, 2026
developmentgoapi

Works with

  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 3, 2026

npx -y skills add HoangNguyen0403/agent-skills-standard --skill specialist-test-gap-finder --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Specialist Test Gap Finder?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Specialist Test Gap Finder
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hoangnguyen0403-specialist-test-gap-finder/badge)](https://www.skillsdirectory.com/skills/hoangnguyen0403-specialist-test-gap-finder)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: specialist-test-gap-finder
description: Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
metadata:
  internal: true
  triggers:
    keywords:
      - test gap
      - missing tests
      - coverage review
      - assertion quality
---
# Specialist: Test Gap Finder

## **Priority: P1 (HIGH)**

## Role

Review code diffs for missing tests, weak assertions, untested edge cases, and broken test assumptions.

## Budget

- Tool cap: <= 12 calls.
- Read test files only to verify assertion quality.
- Run tests before claiming an existing test fails.
- No sub-agents.
- If no diff or changed files are supplied, return `BLOCKED` instead of guessing scope.

## Checklist

1. Identify changed behavior, public APIs, branches, and error paths.
2. Locate related unit, component, integration, E2E, or mobile tests.
3. Verify meaningful assertions; reject smoke-only coverage for real logic.
4. Exempt pure visual pass-through and deprecated code with machine-verifiable deprecation signal.
5. Suggest concrete test case names and layer, not full unverified code.

## Output

```text
### Test Coverage Findings

#### Missing Tests
- [Severity] [file] - [gap + suggested test]

#### Test Quality Issues
- [Severity] [test_file:line] - [issue]

#### What Looks Good
- [observation]
```

Severity: Major, Minor, Suggestion.

## Anti-Patterns

- No duplicate UI tests when lower-layer logic already covered.
- No failing-test claim unless executed.

Files in this skill

  • SKILL.md1.4 KB
  • evals/evals.json615 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.