What is suggest-manual-tests?

A guide for creating manual test cases from changes in a Git code repository. Manual tests are checks a person performs to confirm that a change works.

Use it to prepare test cases from unstaged or staged changes, a branch comparison, the latest commit, or a chosen commit range.

It turns a code comparison into concrete quality-assurance steps, so important behavior and side effects are less likely to go unchecked.

suggest-manual-tests — Skill for Claude Code by jackfranklin

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add jackfranklin/dotfiles --skill suggest-manual-tests

Clone the repo

git clone --depth 1 https://github.com/jackfranklin/dotfiles

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jackfranklin/dotfiles/suggest-manual-tests.svg)](https://agentmods.dev/skills/jackfranklin/dotfiles/suggest-manual-tests)

Your own site

<a href="https://agentmods.dev/skills/jackfranklin/dotfiles/suggest-manual-tests"><img src="https://agentmods.dev/badge/skills/jackfranklin/dotfiles/suggest-manual-tests.svg" alt="Measured on agentmods" height="20"></a>

Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 708 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00039	$0.00708
Opus 5	$0.00019	$0.00354
Sonnet 5	$0.00008	$0.00142
Haiku 4.5	$0.00004	$0.00071

Measured 8d ago against content hash 7d4c67b3c751, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

suggest-manual-tests scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

claude/skills/suggest-manual-tests/SKILL.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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

Read the full file on GitHub · 52 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

examples/sample-test-plan.md 1.1 KB

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

8d ago First seen · 52 lines · 39 tokens per session scan A 7d4c67b3c751

Subscribe to this mod's changes

suggest-manual-tests is a skill published in the GitHub repository jackfranklin/dotfiles (254 stars, last pushed 6d ago), licensed MIT. It adds 39 tokens to every session and 708 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

suggest-manual-tests