Select and run evidence-bearing Bun tests for Mandu changes.
Scanned 9/9/2026
Install to Claude Code
Skills Directorynpx -y skills add konamgil/mandu --skill mandu-testing --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Mandu Testing?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/konamgil-mandu-testing-dc64b55d)More formats (shields.io, HTML) on the badges page.
---
name: mandu-testing
description: Select and run evidence-bearing Bun tests for Mandu changes.
license: MPL-2.0
---
# Mandu Testing
Use after planning identifies the changed behavior or verification recommends
a test.
- Prefer the smallest test that executes the changed contract, then expand to
the affected package and Golden Path.
- Use `bun test`; do not substitute npm or pnpm runners.
- Test failure paths, scope preservation, and generated-output invariants.
- Do not treat a dry run, fixture string, or missing measurement as successful
runtime evidence.
- ATE and browser-healing experiments are Labs and not part of stable testing.
Finish with `mandu.agent.verify --changed --json --write`.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
