lint

Author: devnook

skills/memory-leak-debugging/SKILL.md

@@ -18,6 +18,7 @@ This skill provides expert guidance and workflows for finding, diagnosing, and f
 ### 1. Capturing Snapshots
 
 When investigating a frontend web application memory leak, utilize the `chrome-devtools-mcp` tools to interact with the application and take snapshots.
+
 - Use tools like `click`, `navigate_page`, `fill`, etc., to manipulate the page into the desired state.
 - Revert the page back to the original state after interactions to see if memory is released.
 - Repeat the same user interactions 10 times to amplify the leak.

skills/memory-leak-debugging/references/memlab.md

@@ -9,6 +9,7 @@
 ## Analyzing Snapshots
 
 You can use the `take_memory_snapshot` tool provided by the `chrome-devtools-mcp` extension to generate heap snapshots during an investigation. To find leaks, you generally need 3 snapshots:
+
 1.  **Baseline:** Before the suspect action.
 2.  **Target:** After the suspect action.
 3.  **Final:** After reverting the suspect action (e.g., closing a modal, navigating away).