test-gap-filler

Discover untested code paths and generate test scaffolds for frontend and backend projects.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/satish-krishna/sigil --skill test-gap-filler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-gap-filler
Source: https://github.com/satish-krishna/sigil/tree/main/.claude/plugins/bob/skills/test-gap-filler
Command: npx skills add https://github.com/satish-krishna/sigil --skill test-gap-filler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams improve test coverage by locating untested code paths and generating tests that exercise those areas, ensuring safer, more reliable codebases.

Core Features & Use Cases

  • Automated gap discovery: scans projects to identify missing tests based on common file naming conventions.
  • Test scaffolding: creates or suggests test templates that align with team patterns (e.g., *.spec.ts, *.test.ts, *Tests.cs).
  • Quality-first: ensures new tests pass immediately, prioritizes coverage gaps, and supports rapid iteration.

Quick Start

Run the gap-filler on your repository to generate tests for uncovered code paths.

Frequently Asked Questions about test-gap-filler

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

FAQPage Schema
How do I find untested code paths in my frontend and backend codebase?

Automated gap discovery scans projects to identify untested code paths by analyzing common test file naming conventions like component.spec.ts and EndpointTests.cs, then reports gaps for future iteration.

How do I auto-generate test scaffolds for missing coverage areas?

Test scaffolding creates targeted test templates that align with team patterns such as *.spec.ts and *Tests.cs, generating test scaffolds that follow AAA patterns and project conventions to improve coverage.

Does QA automation test generation work with both TypeScript and C# test naming patterns?

Yes, gap-filling identifies missing tests based on common file naming conventions across frontend and backend codebases, recognizing patterns like service.spec.ts for TypeScript and EndpointTests.cs for C# projects.

How do I ensure auto-generated tests pass immediately and follow project conventions?

Quality-first test generation implements strict QA by ensuring new tests pass immediately, following AAA patterns and project conventions while producing targeted test scaffolds for uncovered code paths.

What is the best way to fill test coverage gaps across a full stack codebase?

Automated gap discovery scans full stack projects to identify missing tests based on file naming conventions, then generates targeted test scaffolds that exercise untested areas for safer, more reliable codebases.

Can I use test gap filling to iterate on coverage gaps over multiple runs?

Yes, the tool supports rapid iteration by reporting gaps for future iteration, prioritizing coverage gaps, and ensuring new auto-generated tests pass immediately on each successive run.