From memory-leak-detector
Detects memory leaks in Node.js, Python, and JVM apps by analyzing event listeners, closures, unbounded caches, and retained references. Use for troubleshooting memory growth.
How this skill is triggered — by the user, by Claude, or both
Slash command
/memory-leak-detector:detecting-memory-leaksThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Detect and diagnose memory leaks in Node.js, Python, and JVM applications by analyzing event listeners, closures, unbounded caches, and retained references.
Detect and diagnose memory leaks in Node.js, Python, and JVM applications by analyzing event listeners, closures, unbounded caches, and retained references.
This skill helps you identify and resolve memory leaks in your code. By analyzing your code for common memory leak patterns, it can help you improve the performance and stability of your application.
This skill activates when you need to:
User request: "detect memory leaks in my event handling code"
The skill will:
User request: "analyze memory usage to find excessive cache growth"
The skill will:
This skill can be used in conjunction with other performance analysis tools to provide a comprehensive view of application performance.
If memory leak detection fails:
5plugins reuse this skill
First indexed Jul 10, 2026
npx claudepluginhub luxdevnet/claude-plus-lux --plugin memory-leak-detectorDetect potential memory leaks and analyze memory usage patterns in code. Use when troubleshooting performance issues related to memory growth or identifying leak sources. Trigger with phrases like "detect memory leaks", "analyze memory usage", or "find memory issues".
Diagnoses memory leaks in JavaScript/Node.js applications using heap snapshots and memlab. Guides through capturing snapshots, running memlab, and identifying common leak causes.
Detect and fix memory leaks using heap snapshots, memory profiling, and leak detection tools. Use when investigating memory growth, OOM errors, or optimizing memory usage.