Menu

Individual skill

create-test

Define or implement regression proof: test strategy, black-box or integration tests, KPIs, thresholds, audits, or missing tests.

plugins/reidemeister94/development-skills/skills/create-test/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,537
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Create test

Start with the user need or business rule that must always hold, not files, coverage, or internal calls.
Inspect for facts; ask only for business decisions that cannot be discovered.

## Definition of done

Agree on the observable result, the oracle that decides correctness, and exact checks before implementation.
Record the environment, data, expected result, unchanged behavior, and limits of the checks.
Use existing checks where they provide evidence. Ask for business rules and acceptance criteria that the evidence cannot settle.
For a bug, reproduce the failure. For new behavior, use agreed examples and show the acceptance check fails before the change.
For a refactor, keep the characterization baseline green before and after the change.
Record each intended behavior difference with its reason and a concrete before and after.