agentsclimarketplace
Sign in

Testing mutation

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

Mutation-testing workflow for exposing weak assertions and missing behavioral checks. Use when tests pass but confidence is low and objective robustness evidence is needed; do not use before baseline tests exist.From its SKILL.md

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

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

1.9 KB, 334 tokens by cl100k_base, as published. Nobody here has run it

Testing Mutation

Overview

Use this skill to quantify test effectiveness and prioritize strengthening weak assertions.

Scope Boundaries

  • Use when pass-only test status is insufficient for confidence.
  • Typical requests:
    • Find weak tests that do not fail when behavior is changed.
    • Use surviving mutants to guide assertion hardening.
    • Quantify test robustness for critical modules.
  • Do not use when:
    • Baseline unit/integration coverage is missing.
    • The primary goal is load or capacity benchmarking (performance-*).

Inputs

  • Existing tests and module criticality
  • Mutation tooling constraints and runtime budget
  • Release risk tolerance

Outputs

  • Mutation report with surviving mutant triage
  • Decision record for target score and remediation strategy
  • Verification checklist for strengthened assertions

Workflow

  1. Select mutation scope by business risk and runtime budget.
  2. Define acceptable mutation score and exception policy.
  3. Run mutation analysis and triage surviving mutants.
  4. Strengthen tests or implementation assertions based on triage.
  5. Re-run and publish deltas, residual risk, and follow-up plan.

Quality Gates

  • Surviving mutants are triaged with explicit rationale.
  • Critical-path mutants have remediation plan.
  • Runtime cost is balanced with risk coverage.
  • Evidence is reproducible and comparable over time.

Failure Handling

  • Stop when critical survivors remain without remediation owner.
  • Escalate when mutation runtime cost blocks practical adoption.

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.