메뉴
Generate a focused manual test plan from the current branch diff. Use when the user asks for a test plan, QA checklist, or manual testing steps for their changes. Includes API/integration host testing when the diff touches relevant endpoints.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Validate the branch diff against the task's acceptance criteria before marking it done. Use when implementation looks complete, before a status update to done/awaiting_review, or when the user asks "did we cover everything?"
Get a PR to merge-ready state by triaging comments, resolving conflicts, and fixing CI. Includes Graphite detection, migration conflict handling, and conflict resolution. Use when the user asks to babysit a PR, get a PR merge-ready, or fix CI on a PR.
Audit implementation plans for the current user, verify status against the codebase, and archive completed plans. Use when the user asks to clean up plans, audit plan status, or archive completed plans.
One-pass AI code review of a PR or branch diff (tech-lead style). Use when the user asks for a code review, PR review, AI review, or wants code quality, architecture, bugs, and patterns reviewed.
Simplify changed code in a PR or branch for readability while preserving behavior. Use when the user asks to simplify code, reduce complexity, clean up a PR, or improve readability of recent changes.
Capture new project-specific learnings into context files. Runs during reviews or after debugging to evolve the project's skill knowledge base. Use when the thread reveals patterns, anti-patterns, conventions, or codebase gotchas that should be remembered.
| name | manual-test-plan |
| description | Generate a focused manual test plan from the current branch diff. Use when the user asks for a test plan, QA checklist, or manual testing steps for their changes. Includes API/integration host testing when the diff touches relevant endpoints. |
Generate a focused manual test plan from the branch diff vs main.
DIFF_BASE=$(gt parent --no-interactive 2>/dev/null || echo "main")
git --no-pager diff "$DIFF_BASE"...HEAD
Review the diff and create a focused manual test plan using the structured format below.
If the diff touches API/integration endpoints (see context.md for detection rules), add a dedicated integration test section. Tailor tests to the changed operations or routing logic.
Use the heading-based format so the run-e2e-plan skill can parse and automate these tests via Playwright:
#### Test 1: [Short test name]
- **Steps**: [Semicolon-separated user actions, e.g. Navigate to /settings; Click "Save"]
- **Expected**: [What should be true after steps]
- **Screenshot**: `[filename-stem]`
Group tests by changed area. For each area, cover:
These test plans can be executed automatically via the run-e2e-plan skill, which generates Playwright scripts from the
structured format, runs them headless with screenshots, and reports pass/fail results. Tests with the Screenshot field
produce visual evidence in e2e/results/.
Integration/API host tests are not Playwright-automatable — they require manual testing in the relevant client environment. See context.md for project-specific integration testing details (detection rules, setup, output format).
Read context.md and apply it as additional project-specific constraints layered on top of this
workflow. If it does not exist, skip this section.