Detect test coverage gaps and create test-only PRs in the wolfe-pack repository.
npx skills add https://github.com/jdforsythe/wolfe-pack --skill wolfe-test-gaps
Please help me install this Agent Skill. Skill: wolfe-test-gaps Source: https://github.com/jdforsythe/wolfe-pack/tree/main/templates/bots/wolfe-test-gaps Command: npx skills add https://github.com/jdforsythe/wolfe-pack --skill wolfe-test-gaps
This Skill identifies and addresses untested public exports, missing error/rejection-path coverage, weak or proxy assertions, snapshot-only specs, and dead/skipped tests, thereby enhancing the robustness of test suites within the wolfe-pack framework.
To initiate a test gap analysis in the 'core' area, use the command: /wolfe-test-gaps core
High-intent search queries and answers about installing and using this skill.
Automated test gap detection scans your repository for untested public exports, missing error and rejection paths, weak assertions, and snapshot-only specs to identify critical coverage gaps. It targets public API surfaces and error paths to ensure comprehensive test suite robustness.
Yes, test gap analysis automatically creates test-only pull requests for identified coverage gaps, ensuring minimal impact on production code. This automated test PR creation targets untested areas while keeping changes isolated to test files.
To initiate a test gap analysis in a specific area, use the command syntax `/wolfe-test-gaps core`, replacing 'core' with your target area. This triggers the scan for untested exports, error paths, and weak assertions within that scope.
Yes, test gap analysis requires access to the repository's WOLFE.md file and the wolfe-pack tooling. These dependencies provide the necessary context and framework integration to scan for coverage gaps and generate test-only PRs.
Test gap analysis detects untested public exports, missing error and rejection-path coverage, weak or proxy assertions, snapshot-only specs, and dead or skipped tests. These categories represent critical areas where test suites lack robustness and faithful verification.
The verification process ensures each test fails before passing, adhering to the principles of faithful testing. This approach validates that newly created tests genuinely catch regressions rather than functioning as weak proxy assertions or snapshot-only specs.
jdforsytheScan codebases to identify and verify bugs with reproducer tests.
haakonbullRefactor Python pytest suites by merging overlaps, parameterizing duplicates, and pruning dead coverage.
Sheldon-92Execute test suites and report failures with coverage metrics.
manastalukdarAnalyze code test coverage and identify untested code paths.
