write-tests

Audit branch coverage, generate missing tests, and verify all tests pass.

1|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/HYP3R00T/voicepad --skill write-tests-hyp3r00t
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-tests
Source: https://github.com/HYP3R00T/voicepad/tree/main/.agents/skills/write-tests
Command: npx skills add https://github.com/HYP3R00T/voicepad --skill write-tests-hyp3r00t

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit test coverage for a stage or file by reading branches, identify gaps, write missing tests, and verify all tests pass. Use this skill whenever the user wants to add tests, check coverage, fill test gaps, or ensure a file is properly tested. Triggers on: "write tests", "add tests", "fill test gaps", "check coverage", "make sure this is tested", "tests are missing", or any request to improve test coverage for a specific file or stage.

Core Features & Use Cases

  • Read the source, map every branch to an existing test, identify coverage gaps, and generate missing tests that exercise decision points and edge cases.
  • Verify that all tests pass after the newly added tests are written, and provide actionable feedback to improve coverage beyond the happy path.
  • Use Case: When a project notices flaky tests or uncovered branches in critical modules, run this skill to systematically increase meaningful branch coverage.

Quick Start

Run the write-tests skill against a codebase to audit coverage and generate missing tests, then run the test suite to verify all tests pass.

Frequently Asked Questions about write-tests

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

FAQPage Schema
How do I automatically generate missing unit tests to improve branch coverage?

To improve branch coverage, this skill audits source code to map every branch to existing tests, identifies coverage gaps, and deterministically generates missing unit tests targeting edge cases and decision points.

What is the best way to find untested branches in a critical module?

The best way to find untested branches is auditing the source file to map decision points against existing tests, which identifies exact coverage gaps beyond the happy path for unit and integration tests.

Can I use this to fill test gaps for both unit and integration tests?

Yes, you can fill test gaps across both unit and integration tests. The skill mirrors source and test paths to generate missing tests and verifies that all tests pass after generation.

How do I verify that newly generated tests actually pass?

To verify newly generated tests pass, the skill executes the test suite immediately after writing missing tests, providing actionable feedback to ensure branch coverage criteria are successfully met.

Does this tool work with existing test files or only generate new ones?

This tool works with existing test files by mapping source branches to current tests to identify gaps, then fills those specific gaps by generating missing tests and verifying the entire suite passes.