edge-case-tests

Name: edge-case-tests
Availability: InStock
Author: thegeronimo

Propose adversarial, invariant, and boundary-case tests for ticket acceptance coverage.

44|8|Updated Jul 14, 2025

Search Tags:#multi-agent #quality-assurance #test-writing #edge-case #acceptance-testing #adversarial-testing #boundary-case

Ready to run

npx skills add https://github.com/thegeronimo/hyperopen --skill edge-case-tests

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: edge-case-tests
Source: https://github.com/thegeronimo/hyperopen/tree/main/.agents/skills/edge-case-tests
Command: npx skills add https://github.com/thegeronimo/hyperopen --skill edge-case-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Proposes adversarial, boundary-case, and invariant test coverage to complement acceptance tests without modifying production code.

Core Features & Use Cases

Propose adversarial, boundary-case, and invariant tests for a given ticket to extend acceptance criteria.
Provide deterministic, review-ready artifacts for multi-agent planning.
Ensure guardrails by not materializing tests or editing production code.

Quick Start

Propose adversarial, invariant, and boundary-case tests for the current ticket without modifying production code.

Frequently Asked Questions about edge-case-tests

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

FAQPage Schema

How do I generate edge-case tests for multi-agent ticket workflows?▼

To generate edge-case tests for multi-agent ticket workflows, you can use a skill that proposes adversarial, invariant, and boundary-case test ideas. It outputs deterministic artifacts to ensure coverage for determinism, ordering, recovery, and safety across agents.

What are adversarial and boundary-case tests in acceptance testing?▼

Adversarial and boundary-case tests in acceptance testing are scenarios designed to probe the limits of ticket criteria. They propose invariant checks and boundary conditions to ensure multi-agent systems handle safety, recovery, and ordering correctly.

Can I propose invariant tests without modifying production code?▼

Yes, you can propose invariant tests without modifying production code. The skill specifically operates under guardrails that avoid editing production code, outputting review-ready proposals instead of materializing the tests directly.

What is the best way to strengthen ticket acceptance coverage for multi-agent systems?▼

The best way to strengthen ticket acceptance coverage is to propose adversarial, invariant, and boundary-case tests. This approach ensures multi-agent workflows have deterministic coverage for ordering, recovery, and safety without altering production code.

Does the edge-case-tests skill write or execute test code?▼

No, the edge-case-tests skill does not write or execute test code. It operates under strict guardrails to avoid materializing tests or editing production code, strictly producing a review-ready proposal artifact.

How do I extend acceptance criteria with boundary-case test proposals?▼

To extend acceptance criteria with boundary-case test proposals, apply a skill that generates adversarial and invariant test ideas. It creates a deterministic proposal artifact to complement existing acceptance tests for multi-agent ticket workflows.