agentsclimarketplace
Sign in

Testing unit

Skill planifest/planifest-framework/planifest-framework/external-skills/testing-unit

Deterministic unit-test strategy for isolated logic and fast feedback. Use when core logic branches, error paths, and edge conditions need low-latency regression evidence with controlled dependencies; do not use for browser-flow or cross-service compatibility validation.From its SKILL.md

Install
npx -y skills add planifest/planifest-framework --skill testing-unit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 341 tokens by cl100k_base, as published. Nobody here has run it

Testing Unit

Overview

Use this skill to validate small-scope logic quickly and deterministically with strong failure localization.

Scope Boundaries

  • Use when correctness can be validated within isolated units.
  • Typical requests:
    • Harden branch and edge-case logic with fast deterministic tests.
    • Verify exception paths and guard-rail behavior.
    • Isolate dependencies to pinpoint failure causes.
  • Do not use when:
    • Cross-service compatibility is the core risk (testing-contract/testing-integration).
    • Full UI journey behavior is needed (testing-e2e/playwright).

Inputs

  • Unit boundaries and behavior expectations
  • Mock/stub strategy and dependency seams
  • Runtime constraints for fast feedback loops

Outputs

  • Unit suite with fixture and isolation strategy
  • Decision record for scope and assertion depth
  • Verification checklist for edge/failure coverage

Workflow

  1. Identify unit boundaries and observable contracts.
  2. Define edge and failure conditions before implementation.
  3. Compare isolation strategies and choose one with rationale.
  4. Implement deterministic tests with explicit assertions.
  5. Publish residual risks and uncovered dependency behaviors.

Quality Gates

  • Unit scope is explicit and dependency control is intentional.
  • Edge and failure cases are covered for critical logic.
  • Tests are deterministic and fast enough for frequent execution.
  • Evidence is reproducible and actionable.

Failure Handling

  • Stop when critical units lack edge/failure coverage.
  • Escalate when isolation requires architectural refactoring.

Bundled Resources

  • references/trigger-and-examples.md: trigger patterns, anti-patterns, and deliverable expectations.

What ships with it: 1 file

11.3 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,750. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.