skills/chromedevtools__chrome-devtools-mcp
1
0
Fork 0
mirror of https://github.com/ChromeDevTools/chrome-devtools-mcp.git synced 2026-09-14 19:45:30 +08:00
Code Issues Packages Projects Releases Wiki Activity

fix(memory): expliclity mention the need of a flag (#2620)

Browse Source 
Currently if the generic DevTools SKILL is not in the context the LLM
just drop trying to find the tools.
Giving this hit allows it to prompt the user for a change. This still
will require a restart for now.
This commit is contained in:
Nikolay Vitkov
2026-08-27 11:30:21 +00:00
committed by GitHub
parent 2dc104ce1b
commit 46c3e05ade
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/memory-leak-debugging/SKILL.md
+4
View File
@@ -7,6 +7,10 @@ description: Diagnoses and resolves memory leaks in JavaScript/Node.js applicati
This skill provides expert guidance and workflows for finding, diagnosing, and fixing memory leaks in JavaScript and Node.js applications using Chrome DevTools MCP tools.
## Prerequisites
Advanced memory debugging tools (`compare_heapsnapshots`, `get_heapsnapshot_details`, etc.) are only available when the server is started with the `--memoryDebugging` flag. First check if these tools are available; if not, try to read the MCP configuration file to check if `--memoryDebugging` is enabled.
## Core Principles
- **Prefer MCP memory tools:** Do NOT attempt to read raw `.heapsnapshot` files directly, as they are extremely large and will consume too many tokens. Use the Chrome DevTools MCP heap snapshot tools to summarize, compare, and inspect snapshots.