suggest-manual-tests

Use when the user wants to generate manual test cases, QA steps, or test plans based on a git diff of latest commits, branch comparison, or unstaged changes.

Jump to install

Repository: jackfranklin/dotfiles
Last source activity: June 27, 2026 at 22:01
Detected SKILL.md language: English
Stars: 254
Forks: 33

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/jackfranklin/dotfiles --skill suggest-manual-tests

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

Suggest Manual Tests Skill

Use this skill when the user requests manual test cases or QA verification steps to test recent changes.

Workflow

Retrieve the Git Diff: Ask the user which git diff they would like to use:

1. Unstaged changes (git diff)
1. Staged changes (git diff --cached)
1. Branch comparison vs origin/main (git diff origin/main...)
1. Latest commit (git diff HEAD~1)
1. Custom range (e.g., specific commits or branch)

If the user has already specified which diff to use, skip the question and retrieve the diff using the corresponding git command. Save the output as DIFF_CONTENT.

If the diff is empty, notify the user and ask them to make changes or provide a valid ref.

Analyze the Diff: Analyze the files and code modified in DIFF_CONTENT. For each modified component, function, endpoint, or page, identify:

Logical behavior: What changed?
User interface: Are there styling or interactive changes?
Side-effects: Does it change state, call APIs, send analytics, read/write storage?
Dependencies: What other parts of the system consume this modified code?

Generate Manual Test Cases: Create a structured, succinct list of manual test cases. For each logical/functional change, provide:

Test Case ID & Title: Short, clear name (e.g., TC01: Verify Form Validation on Error).
Scope: What specific bug, feature, or code change is being verified.
Prerequisites / Setup: Any local database, env variable, config change, mock data, or state required before starting.
High-Level Steps: Concise instructions. Do NOT detail menial UI clicks (e.g. "click button X and then click Y"). Assume the developer/tester knows how to operate the application/tool.
Expected Result: Clear description of what should happen (visual verification, console logs, network requests, database changes).

Guidelines:

Keep it succinct: Focus on manual-specific verification that automated tests might not cover well (e.g. UI layout, accessibility, interactions, complex flows).
Offer edge cases: If there are many manual edge cases, present the core cases first and explicitly ask the user if they want the full set of edge cases.

Present Results: Present the generated manual test cases directly inline in the chat. Do NOT save them to a file or write them to disk.

Examples

Refer to sample-test-plan.md for a reference implementation of high-level manual testing scenarios.