Skip to content
Agentmart
Submit a tool

property-based-testing

Design or review generative tests for parsers, validators, transformations, state machines, calculations, permissions, and business rules.

Skill by NeroWasTrolled

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/nerowastrolled-property-based-testing

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Design or review generative tests for parsers, validators, transformations, state machines, calculations, permissions, and business rules. Use Hypothesis for Python or fast-check for TypeScript when available.

Use cases: design, testing

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/property-based-testing

What's inside

Skill name
property-based-testing
Description
Design or review generative tests for parsers, validators, transformations, state machines, calculations, permissions, and business rules. Use Hypothesis for Python or fast-check for TypeScript when available.
License
MIT
Instructions
21 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Property-Based Testing

Express behavior as invariants over a meaningful input domain.

1. Identify the contract and invariants: round trips, idempotence, monotonicity,
   conservation, ordering, equivalence, or forbidden states.
2. Define generators that reflect valid, invalid, boundary, and adversarial data.
3. Constrain inputs only where the real domain requires it; do not filter away
   the bug surface.
4. Use an independent oracle, model, metamorphic relation, or differential
   implementation when possible.
5. Confirm a failure shrinks to a useful minimal example and preserve it as a
   regression example when valuable.
6. Run examples alongside property tests; neither replaces the other.

Reject tautologies such as comparing a function to itself, properties that are
true only because generators never reach difficult cases, and excessive mocks
that bypass the behavior under test. Record seeds or counterexamples when the
framework does not persist them automatically.

From NeroWasTrolled/gabriel-ai-devkit, MIT.

More from NeroWasTrolled/gabriel-ai-devkit

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Sep 3, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/NeroWasTrolled/gabriel-ai-devkit
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from NeroWasTrolled

Cite this page

property-based-testing skill. Agent Mart. https://agentmart.dev/skills/nerowastrolled-property-based-testing (last updated 2026-10-24)