ywc-gen-testcase

Generate dual-audience Markdown testsheets from GitHub PRs, task directories, git ranges, or diffs.

8|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-gen-testcase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ywc-gen-testcase
Source: https://github.com/yongwoon/ywc-agent-toolkit/tree/main/claude-code/skills/ywc-gen-testcase
Command: npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-gen-testcase

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes references (resource) components.

What problem does it solve?

This Skill solves the disconnect between developer verification and QA validation by automatically generating a structured, dual-audience testsheet that separates pre-merge technical checks from pre-release user-facing scenarios.

Core Features & Use Cases

  • Dual-Audience Gates: Automatically splits verification into a Developer section (API, DB, logs) and a QA section (UI, browser-observable effects).
  • Intelligent Input Resolution: Generates testsheets from GitHub PRs, specific task directories, git ranges, or current diffs.
  • Tiered Layouts: Automatically adjusts the testsheet structure based on complexity, ensuring readability for both small PRs and massive releases.

Quick Start

Use the ywc-gen-testcase skill to generate a verification testsheet for the current pull request number 250.

Frequently Asked Questions about ywc-gen-testcase

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

FAQPage Schema
How do I generate a QA testsheet from a GitHub pull request?

To generate a QA testsheet from a GitHub pull request, you can use an automated tool to parse PR diffs and create a dual-audience Markdown document. This separates pre-merge developer checks from pre-release QA scenarios for comprehensive sign-off.

What is a dual-audience testsheet for pre-merge and pre-release gates?

A dual-audience testsheet is a Markdown document that splits verification into developer checks and QA scenarios. It classifies backend contract validations separately from browser-observable UI effects to facilitate parallel sign-off during pre-merge and pre-release gates.

Can I create verification testsheets from git ranges or current diffs?

Yes, you can create verification testsheets from git ranges or current diffs. The generation process intelligently resolves inputs from GitHub PRs, specific task directories, or direct git diffs to structure your verification scenarios effectively.

How do I maintain testsheet readability for large software releases?

To maintain testsheet readability for large releases, the generation process implements tiered layout logic and length management guidelines. This automatically adjusts the documentation structure based on complexity to ensure quality across varying project scales.

Does the testsheet generation require the GitHub CLI to run?

Yes, the testsheet generation requires the GitHub CLI (`gh`) to run. You need this dependency installed to fetch pull request data, resolve task directories, and automatically generate the structured Markdown testsheet.