cover
FeaturedGenerate tests that do not exist yet. Analyzes coverage gaps, then writes and runs new test files across three tiers (unit, integration via testcontainers, Playwright E2E), one test-generator agent per tier, healing failures for up to 3 iterations. Use when code has no tests or when raising coverage after implementation. Do NOT use to grade tests that already exist (use /ork:verify) or to run a suite without writing anything new.
Install
Quality Score: 91/100
Skill Content
Details
- Author
- yonatangross
- Repository
- yonatangross/orchestkit
- Created
- 8 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
cover
Generate, execute, and heal test suites across unit, integration, and E2E tiers. Automated failure healing, coverage comparison, fingerprint caching, and ARIA accessibility diffing. Supports --target for autonomous coverage improvement and --streak to require N consecutive green runs before a test is kept. Use when: adding tests, increasing coverage, generating test files, or validating untested code. Triggers on: cover, generate tests, test coverage, write tests, add tests, untested, increase coverage, coverage target, E2E tests, Playwright, flaky test, streak gate
generate-tests
Generate unit tests for a .NET service following the coverage-kit conventions. Use when the user asks to 'generate tests', 'backfill tests', 'characterize this service', or 'add tests for' a target after coverage-init has run. Operates in characterization mode (freeze current behavior for existing code) or spec mode (assert intended behavior for new/changed code), enforces the run-capture-fill loop, routes untestable units to the manifest cannot-test log, can fan the backfill out across a user-chosen number of parallel agents for large worklists (asking first, since more agents cost more tokens), and runs a single read-only suite critique before the baseline locks in (auditing cannot-test legitimacy, assertion/C1 depth, systematic gaps, and any frozen defect missing from the manifest latent_bugs backlog, never the C0/C1 numbers themselves).
add-tests
Discover the project's coverage command, rank under-covered files by risk, resolve a mocking convention per ecosystem, and hand the findings to to-issues as ready-for-agent issues. Use when the user wants to close testing-coverage gaps or asks to find where test coverage is weakest.