memory-leak-audit
The #1 bug category in VS Code. This skill encodes the patterns that prevent and fix leaks.
SkillJury keeps community verdicts, source metadata, and external repository signals in separate lanes so ranking data never pretends to be a review.
No approved reviews yet
Waiting on enough review volume
Weekly or total install activity from catalog data
npx skills add https://github.com/microsoft/vscode --skill memory-leak-audit
As of Apr 30, 2026, memory-leak-audit has 727 weekly installs, 0 community reviews on SkillJury. Community votes currently stand at 0 upvotes and 0 downvotes. Source: microsoft/vscode. Canonical URL: https://skills.sh/microsoft/vscode/memory-leak-audit.
Source description provided by the upstream listing. Community review signal and install context stay separate from this narrative layer.
Latest reviews
No community reviews yet. Be the first to review.
What does memory-leak-audit do?
The #1 bug category in VS Code. This skill encodes the patterns that prevent and fix leaks.
Is memory-leak-audit good?
memory-leak-audit does not have approved reviews yet, so SkillJury cannot publish a community verdict.
Which AI agents support memory-leak-audit?
memory-leak-audit currently lists compatibility with Skills CLI.
Is memory-leak-audit safe to install?
memory-leak-audit has been scanned by security audit providers tracked on SkillJury. Check the security audits section on this page for detailed results from Socket.dev and Snyk.
What are alternatives to memory-leak-audit?
Skills in the same category include grimoire-morpho-blue, conversation-memory, second-brain-ingest, zai-tts.
How do I install memory-leak-audit?
Run the following command to install memory-leak-audit: npx skills add https://github.com/microsoft/vscode --skill memory-leak-audit
More from microsoft/vscode
fix-errors
When fixing an unhandled error from the telemetry dashboard, the issue typically contains an error message, a stack trace, hit count, and affected user count.
azure-pipelines
When modifying Azure DevOps pipeline files (YAML files in build/azure-pipelines/ ), you can validate changes locally using the Azure CLI before committing. This avoids the slow feedback loop of pushing changes, waiting for CI, and checking results.
sessions
Source details, install context, and public review data are available on the full page.
agent-sessions-layout
Source details, install context, and public review data are available on the full page.
Alternatives in Software Engineering
grimoire-morpho-blue
Query Morpho Blue deployment metadata and vault snapshots via the Grimoire CLI.
conversation-memory
Persistent memory systems for LLM conversations with tiered storage and intelligent retrieval.
second-brain-ingest
Process raw source documents into structured, interlinked wiki pages.
zai-tts
High-quality text-to-speech audio generation using GLM-TTS with customizable voices and playback parameters.