skills.rest
Olshansk
OlshanskCOMMUNITY
Explore all skills by this author →
Website𝕏@OlshanskyGitHub

cmd-pr-test-plan

Generate manual test plans for pull request changes with pass/fail criteria.

8|Updated Jan 22, 2026
Search Tags:#automation#git#testing#code review#documentation#pr
One-click install
npx skills add https://github.com/Olshansk/agent-skills --skill cmd-pr-test-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cmd-pr-test-plan
Source: https://github.com/Olshansk/agent-skills/tree/main/skills/cmd-pr-test-plan
Command: npx skills add https://github.com/Olshansk/agent-skills --skill cmd-pr-test-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of manual test plans for pull request changes, ensuring thorough verification by reviewers.

Core Features & Use Cases

  • Automated Test Plan Generation: Creates detailed, step-by-step test plans based on code changes.
  • Clear Verification Criteria: Includes copy-paste commands and explicit pass/fail conditions.
  • Use Case: Before merging a new feature, use this Skill to generate a comprehensive test plan that a QA engineer can follow to validate the changes, ensuring all aspects of the feature work as expected.

Quick Start

Use the cmd-pr-test-plan skill to generate a manual test plan for the current branch.

Frequently Asked Questions about cmd-pr-test-plan

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

FAQPage Schema
How do I generate a manual test plan for a pull request?▼

To generate a manual test plan for a pull request, this Skill analyzes git diff and log data to produce a structured TEST_PLAN.md file with copy-paste commands and explicit pass/fail criteria for reviewers.

How does test plan generation work with existing project tooling?▼

Test plan generation detects project tooling like Makefiles, package managers, and test runners to categorize code changes and provide relevant, structured verification steps tailored to your specific development environment.

Can I use this to create test plans for QA engineers before merging?▼

Yes, you can use this to create test plans for QA engineers before merging by generating comprehensive, step-by-step verification instructions based directly on the detected branch changes.

What is the best way to automate pull request verification criteria?▼

The best way to automate pull request verification criteria is to detect base branches, gather change context via git diff, and output structured pass/fail conditions alongside copy-paste terminal commands.

Does generating a PR test plan require any dependencies?▼

Generating a PR test plan requires no external dependencies, relying solely on your project's existing git history, base branches, and detected tooling to build the structured manual test plan.

Why use automated test plan generation instead of manual documentation?▼

Automated test plan generation categorizes git changes and outputs a TEST_PLAN.md with a terminal summary, preventing human error and ensuring thorough verification by reviewers without manual documentation effort.

Related Skills

Explore More Software Engineering Skills→
vincent-kkvincent-kk
1

git-change-analyzer

Aggregate Git commits, branch diffs, and staged changes into JSON.

Community
Basic
m16khbm16khb

finishing-a-development-branch

Run the test suite and present four options for merging, PR, keeping, or discarding a branch.

Community
Advanced
racecraft-labracecraft-lab
3

speckit-resolve-pr

Resolve unresolved pull request review threads with minimal code changes.

Official
Advanced
adiytharpansaadiytharpansa

testing-framework

Generate and validate unit, integration, and end-to-end test suites.

Community
Advanced