Zerg testing workflow (unit + E2E). Use when running or debugging tests.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add cipher982/longhouse --skill zerg-testing --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Zerg Testing?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cipher982-zerg-testing)More formats (shields.io, HTML) on the badges page.
---
name: zerg-testing
description: Zerg testing workflow (unit + E2E). Use when running or debugging tests.
---
# Zerg Testing
## Rules
- Always use Make targets. Never run pytest/bun/playwright directly.
## Core Commands
```bash
make test # unit tests
make test-e2e-core # core E2E (must pass 100%)
make test-e2e # full E2E (retries ok)
make test-full # unit + full E2E + visual checks
make test-e2e-single TEST=tests/<spec>.ts
make test-e2e-errors # show last E2E errors
make test-e2e-verbose # full output for debugging
```
## Debugging Flow
1) `make test-e2e-errors`
2) `make test-e2e-single TEST=tests/<spec>.ts`
3) `make test-e2e-verbose`
## Flake Policy
- Keep core E2E at retries=0. If a CI failure passes on rerun with no code
diff, quarantine or move that test out of the blocking lane the same day and
leave a tracking issue; do not normalize red-but-ignored CI.
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!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...