memory-leak-audit Skill
Audit code for memory leaks and disposable issues. Use when reviewing event listeners, DOM handlers, lifecycle callbacks, or fixing leak reports. Covers addDisposableListener, Event.once, MutableDisposable, DisposableStore, and onWillDispose patterns. Published by microsoft in vscode.
Decision snapshot
Is this a fit?
Security review, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
1 month ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is memory-leak-audit Skill?
Audit code for memory leaks and disposable issues. Use when reviewing event listeners, DOM handlers, lifecycle callbacks, or fixing leak reports. Covers addDisposableListener, Event.once, MutableDisposable, DisposableStore, and onWillDispose patterns. Published by microsoft in vscode. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Security review
- Security review use cases
Declared skill metadata
- Source file: .github/skills/memory-leak-audit/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use memory-leak-audit Skill
- Use it for security review.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode
- Skill file: .github/skills/memory-leak-audit/SKILL.md
What it does
Audit code for memory leaks and disposable issues. Use when reviewing event listeners, DOM handlers, lifecycle callbacks, or fixing leak reports. Covers addDisposableListener, Event.once, MutableDisposable, DisposableStore, and onWillDispose patterns.
Skill instructions
Memory Leak Audit The 1 bug category in VS Code. This skill encodes the patterns that prevent and fix leaks. When to Use - Reviewing code that registers event listeners or DOM handlers - Fixing reported memory leaks (listener counts growing over time) - Creating objects in methods that are called repeatedly - Working with model lifecycle events (onWillDispose, onDidClose) - Adding event subscriptions in constructors or setup methods Audit Checklist Work through each check in order. A single missed pattern can cause thousands of leaked objects. Step 1: DOM Event Listeners Rule: Never use raw .onload, .onclick, or addEventListener() directly. Always use addDisposableListener(). typescript // BAD — leaks a listener every call this.iconElement.onload = () = { ... }; // GOOD — tracked and disposable this.register(addDisposableListener(this.iconElement, 'load', () = { ... })); Validated by: PR 280566 — Extension icon widget leaked 185 listeners after 37 toggles. Step 2: One-Time Events Rule:
Verified compatibility and discovery
Frequently asked questions
What is memory-leak-audit?
memory-leak-audit is a open-source AI agent skill with Copy skill directory. Audit code for memory leaks and disposable issues. Use when reviewing event listeners, DOM handlers, lifecycle callbacks, or fixing leak reports.
Who is memory-leak-audit best for?
memory-leak-audit is best for reusing agent instructions, scripts, and references, security review workflows.
How do I install memory-leak-audit?
Install or run memory-leak-audit using Copy skill directory. Check memory-leak-audit for the latest setup command.
Is memory-leak-audit actively maintained?
memory-leak-audit may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.