Test Gaps
- 662 installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
test-gaps is an agent skill that detects missing test coverage and generates test suggestions via claude-flow CLI hooks and MCP worker dispatch for developers finishing features.
About
test-gaps is a ruvnet ruflo skill that finds coverage holes and suggests next tests after feature work. CLI commands include `npx @claude-flow/cli@latest hooks coverage-gaps --format table --limit 20`, `hooks coverage-route --task`, and `hooks coverage-suggest --path src/`. Optional flags `--path PATH` and `--limit N` scope analysis. Alternatively, dispatch the testgaps worker through `mcp__claude-flow__hooks_worker-dispatch`. Developers reach for test-gaps when asking what still needs tests, auditing untested modules, or closing coverage gaps before PR merge. Bash, Read, and Grep permissions support local codebase inspection alongside CLI output.
- test-gaps
Test Gaps by the numbers
- 662 all-time installs (skills.sh)
- +7 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #561 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill test-gapsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 662 |
|---|---|
| repo stars | ★ 67k |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
How do you find untested code before merging?
Use test-gaps for development tasks
Who is it for?
Developers who just shipped a feature and need prioritized test suggestions before opening a pull request.
Skip if: Production error triage or git diff risk review without any test coverage analysis requirement.
When should I use this skill?
The user asks about coverage gaps, untested code, what tests to write next, or after adding a feature without tests.
What you get
Coverage gap tables, scoped test suggestions, and routed test-writing tasks for untested paths.
- coverage gap table
- test suggestion list
- routed test-writing task
By the numbers
- Default coverage-gaps output uses --limit 20 table format
- Exposes 3 claude-flow CLI hooks: coverage-gaps, coverage-route, coverage-suggest
Files
Find test coverage gaps via CLI:
npx @claude-flow/cli@latest hooks coverage-gaps --format table --limit 20
npx @claude-flow/cli@latest hooks coverage-route --task "add auth tests"
npx @claude-flow/cli@latest hooks coverage-suggest --path src/Or dispatch the testgaps worker via MCP: mcp__claude-flow__hooks_worker-dispatch({ trigger: "testgaps" })
For continuous detection, use /loop with the loop-worker skill targeting the testgaps worker.
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kHow it compares
Pick test-gaps over diff-analyze when the question is missing tests rather than merge risk on git diffs.
FAQ
Which CLI commands does test-gaps use?
test-gaps runs `npx @claude-flow/cli@latest hooks coverage-gaps --format table --limit 20`, plus `coverage-route` and `coverage-suggest --path` commands. An MCP testgaps worker dispatch is also available.
When should test-gaps run?
test-gaps runs after adding features or when the user asks about coverage gaps and untested code. Use it before PR merge to prioritize which modules still need test cases.