What problem does it solve? Investigating pnpm test OOMs and RSS spikes in the OpenClaw repo is hard because Vitest worker memory growth can come from either real application leaks or retained transformed-module graphs in long-lived shared workers. This Skill provides a repeatable workflow to reproduce the failing lane, capture heap snapshots, and classify the growth before choosing a fix. ## Core Features & Use Cases - Heap Snapshot Diffing: Compare two .heapsnapshot files directly or auto-select the earliest/latest pair per PID inside a lane directory using the bundled heapsnapshot-delta.mjs script. - Leak Classification Heuristics: Distinguish retained Vite/Vitest transformed-module growth from genuine runtime object leaks, with guidance to confirm ambiguous cases via DevTools retainers and dominators. - Fix Guidance: Apply timing-driven scheduling fixes, singletonIsolated lane peeling via test-parallel behavior fixtures, or patch real cleanup gaps such as missing afterEach hooks and unreleased handles. - Use Case: A CI unit-fast-batch lane OOMs at 6GB. Reproduce with OPENCLAW_TEST_HEAPSNAPSHOT_DIR enabled, diff snapshots per PID, find transformed-module strings dominating the delta, and peel the hotspot file into an isolated lane. ## Quick Start Ask the agent to investigate the OpenClaw test memory growth by reproducing the failing lane with heap snapshots enabled and diffing the snapshots with the heapsnapshot-delta script.