Finding memory leaks in code is critical for keeping applications fast and stable. This skill helps you audit event listeners, DOM handlers, and lifecycle callbacks. It covers patterns like addDisposableListener, Event.once, and MutableDisposable.
You will learn to spot hidden leaks that grow over time. Each step gives clear rules and examples. Use this when reviewing code or fixing reported leak reports.
Global
mkdir -p ~/.claude/skills/memory-leak-auditProject
mkdir -p .claude/skills/memory-leak-auditSource Repository
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Codebase Designmattpocock/skills
Create deep modules with tiny interfaces and lots of hidden logic for testability
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective