# 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.

- Skill: `etanhey/test-plan` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add etanhey/test-plan`
- Raw SKILL.md: https://api.skillmd.com/api/skills/etanhey/test-plan/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: EtanHey (https://skillmd.com/u/etanhey)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/etanhey/test-plan

---


# 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:

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

## What It Does

1. 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/component
4. 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

## Usage

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