heap-snapshot-analysislisted

# Heap Snapshot Analysis Investigate memory leaks from V8 heap snapshots (`.heapsnapshot` files). This skill starts when snapshots already exist: either the user provided them, DevTools exported them, or another workflow produced them. Use the helpers here to compare snapshots, group object deltas, and trace retainer paths. ## IGNORE Prior Investigations **Start every investigation fresh.** Do NOT read, consult, or be influenced by prior investigations found in: - `/memories/` (user, session, or repo memory) - `.github/skills/heap-snapshot-analysis/scratchpad/` (previous dated subfolders and their `findings.md` files) - Any other notes from earlier sessions Previous findings can bias the analysis toward suspects that are no longer relevant, or cause the agent to skip steps and jump to conclusions. Let the current snapshots speak for themselves. Only reference prior work if the user explicitly asks you to. ## When to Use - User provides `.heapsnapshot` files (before/after a workflow) - User has heap snapshots captured by another skill or script - Need to find what retains disposed objects (retainer path analysis) - Comparing object counts/sizes between two snapshots - Investigating why particular objects survive GC ## Workflow If the user needs the agent to launch VS Code, drive a scenario, and capture snapshots first, use the VS Code performance workflow skill before returning here for low-level snapshot analysis. ### 1. Parse Snapshots Use the helpers in [parseSna