write-test

Write tests for untested user-facing features guided by code coverage reports.

19|4|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/wunki/amplify --skill write-test-wunki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-test
Source: https://github.com/wunki/amplify/tree/main/skills/write-test
Command: npx skills add https://github.com/wunki/amplify --skill write-test-wunki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of insufficient test coverage by guiding users to write meaningful tests that focus on user-facing behavior, rather than just increasing line coverage.

Core Features & Use Cases

  • Coverage-Guided Test Writing: Uses code coverage reports to identify untested user-facing features.
  • Prioritizes User Workflows: Focuses on testing critical user interactions and error conditions.
  • Iterative Approach: Encourages writing one test at a time for focused development.
  • Use Case: When a coverage report shows a critical user-facing feature is untested, this skill helps you write a relevant test for it.

Quick Start

Use the write-test skill to add a test for the user login feature.

Frequently Asked Questions about write-test

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

FAQPage Schema
How do I write meaningful unit tests instead of just increasing code coverage?

To write meaningful unit tests, use code coverage as a guide to identify untested user-facing behavior, prioritizing real user workflows and critical features over low-value implementation details.

How do I use code coverage reports to target critical user workflows?

Use code coverage reports to identify untested critical user-facing features. This approach targets real user interactions and error conditions, ensuring tests validate actual behavior rather than merely increasing line coverage.

Does this testing approach work with my existing test runner like vitest or pytest?

Yes, this approach integrates with project-specific test runners and coverage tools like vitest, jest, c8, go, or pytest to analyze reports and guide the creation of relevant behavioral tests.

What is the best way to add tests for untested user-facing features?

The best way to add tests for untested features is an iterative approach. Write one test at a time for focused development, specifically targeting critical user interactions identified in coverage reports.

Why should I prioritize testing user workflows over implementation details?

Prioritizing user workflows over implementation details ensures tests validate critical user-facing behavior and error conditions. This creates meaningful regression testing that protects actual functionality rather than just chasing line coverage.

When should I focus on integration tests versus unit tests for user behavior?

Focus on integration tests or unit tests when a coverage report shows a critical user-facing feature lacks validation. Target real user workflows iteratively, writing one test at a time to address untested behavior.