How do I install the Test Plan skill?

Run npx skillmds@latest add etanhey/test-plan in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Test Plan safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Test Plan?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Test Plan free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Test Plan?

EtanHey (@etanhey) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Test Plan by etanhey — Agent Skill

Name: Test Plan
Author: EtanHey

Test Plan

Generate structured manual testing checklists from git diffs for QA review before merging PRs. Analyzes changed files and produces step-by-step testing instructions covering happy paths, edge cases, and regression checks. Output is a markdown checklist suitable for QA handoff or self-review. Use when preparing a PR for manual QA, creating a testing checklist for a feature branch, or documenting what needs manual verification before merge. Triggers on 'test plan', 'QA checklist', 'testing checklist', 'manual testing', 'QA review prep'. NOT for: writing automated tests (write those in code), AI code reviews (use coderabbit), or CI pipeline configuration.

EtanHey 8bb18f0 4 files · 16.3 KB Updated Sep 17, 2026

File contents

Generate Test Plan

Analyze changes in the current Git branch and generate a manual testing checklist organized by page/feature.

Quick Start

The skill auto-runs on load. Override the base branch:

./scripts/generate.sh --base main
./scripts/generate.sh --base dev
./scripts/generate.sh --base origin/staging

What It Does

Gets the diff against the base branch (default: main)
Categorizes changed files by type (UI, API, DB, Config, etc.)
Generates a Markdown checklist grouped by feature/component
Includes regression test suggestions for related areas

Output Format

## Test Plan

### [Feature/Component Name]
- [ ] Test: Description of what to verify
- [ ] Test: Another thing to check

### API Changes
- [ ] Test: Verify endpoint returns expected shape
- [ ] Test: Error responses have correct status codes

### Database/Schema
- [ ] Test: Verify migrations run cleanly
- [ ] Test: Data integrity after changes

### Configuration
- [ ] Test: Verify env vars are documented
- [ ] Test: Config changes don't break existing deploys

### General
- [ ] No console errors during testing
- [ ] No TypeScript/build errors
- [ ] Mobile responsive (if UI changes)

Guidelines

Be specific: "Verify user can submit form" not "Test form"
Include edge cases: Empty states, error states, loading states
Consider permissions: Test as different user roles if auth-related
Note regressions: If touching shared code, note areas that could regress
Prioritize: Put most critical tests first within each section

Usage

Run this skill before creating a PR to generate the test plan section for your PR description.

---name: test-plandescription: Generate structured manual testing checklists from git diffs for QA review before merging PRs. Analyzes changed files and produces step-by-step testing instructions covering happy paths, edge cases, and regression checks. Output is a markdown checklist suitable for QA handoff or self-review. Use when preparing a PR for manual QA, creating a testing checklist for a feature branch, or documenting what needs manual verification before merge. Triggers on 'test plan', 'QA checklist', 'testing checklist', 'manual testing', 'QA review prep'. NOT for: writing automated tests (write those in code), AI code reviews (use coderabbit), or CI pipeline configuration.---# Generate Test PlanAnalyze changes in the current Git branch and generate a manual testing checklist organized by page/feature.## Quick StartThe skill auto-runs on load. Override the base branch:```bash./scripts/generate.sh --base main./scripts/generate.sh --base dev./scripts/generate.sh --base origin/staging```## What It Does1. Gets the diff against the base branch (default: main)2. Categorizes changed files by type (UI, API, DB, Config, etc.)3. Generates a Markdown checklist grouped by feature/component4. Includes regression test suggestions for related areas## Output Format```markdown## Test Plan### [Feature/Component Name]- [ ] Test: Description of what to verify- [ ] Test: Another thing to check### API Changes- [ ] Test: Verify endpoint returns expected shape- [ ] Test: Error responses have correct status codes### Database/Schema- [ ] Test: Verify migrations run cleanly- [ ] Test: Data integrity after changes### Configuration- [ ] Test: Verify env vars are documented- [ ] Test: Config changes don't break existing deploys### General- [ ] No console errors during testing- [ ] No TypeScript/build errors- [ ] Mobile responsive (if UI changes)```## Guidelines- **Be specific**: "Verify user can submit form" not "Test form"- **Include edge cases**: Empty states, error states, loading states- **Consider permissions**: Test as different user roles if auth-related- **Note regressions**: If touching shared code, note areas that could regress- **Prioritize**: Put most critical tests first within each section## UsageRun this skill before creating a PR to generate the test plan section for your PR description.

Frequently asked questions