write-test-cases

Generates manual test-case specifications with regression suite and coverage map from analyzed codebase.

581|102|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/juicesharp/rpiv-mono --skill write-test-cases
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-test-cases
Source: https://github.com/juicesharp/rpiv-mono/tree/main/packages/rpiv-pi/skills/write-test-cases
Command: npx skills add https://github.com/juicesharp/rpiv-mono --skill write-test-cases

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of manual test case specifications for a single feature by analyzing code in parallel, producing flow-based test cases, a regression suite, and a project-wide coverage map. It outputs artifacts to .rpiv/test-cases/{feature}/ in the target repository.

Core Features & Use Cases

  • Generate end-to-end test cases by inspecting controllers, routes, frontend text, and UI labels to reflect real user interactions.
  • Produce a regression suite and a coverage map to guide QA planning and ensure broad coverage.
  • Leverage _meta.md warm-start data when available to reuse established feature scope, routes, domain context, and checkpoints.

Quick Start

Provide a feature name or code path to begin generating manual test cases.

Frequently Asked Questions about write-test-cases

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

FAQPage Schema
How do I generate manual test cases from source code for a single feature?

Generating manual test cases from source code involves analyzing backend controllers, routes, and frontend UI labels to map real user flows. This skill automates that code analysis to produce flow-based test case specifications, a regression suite, and a coverage map.

Can I warm-start test case generation using existing feature metadata?

Yes, test case generation can warm-start from an optional _meta.md file. This allows the skill to reuse established feature scope, routes, domain context, and checkpoints to accelerate and contextualize the output.

How do I create a regression suite and coverage map from a codebase?

Creating a regression suite and coverage map from a codebase requires analyzing user flows and postconditions across frontend and backend surfaces. This skill outputs both artifacts to .rpiv/test-cases/{feature}/ to guide QA planning.

Does automated test case generation check for duplicates against existing test cases?

Yes, automated test case generation includes steps to check for duplicates against existing test cases. It maps user flows, identifies postconditions, and prioritizes test cases without writing code directly.

What is the best way to turn backend and frontend code into actionable QA test cases?

Turning backend and frontend code into actionable QA test cases is best done by inspecting controllers, routes, frontend text, and UI labels in parallel. This approach ensures generated test cases reflect real end-to-end user interactions.