...when extension tools are missing. I've run into the situation that
the coding agent would try different esoteric approach to install the
extension when asked to debug it in chrome DevTools.
Updates the flag for the memory tooling to remove the experimental bit
(keep alias for backwards compatibility).
And updates the SKILLs to reflected the update names and point to the
available tools.
Q: Should it be called `take_heapsnapshot` or `take_heap_snapshot`?
Extracting WebMCP tools into a separate category for better grouping in
the docs. This changes `--experimentalWebmcp` to
`--categoryExperimentalWebmcp` to align with other experimental
categories. Debugging category was not a good fit since the tools
provided by WebMCP are not necessarily used for debugging.
cc @beaufortfrancois
## Summary
This PR fixes several documentation and skill-reference issues across
the repo to improve accuracy and reduce confusion in implementation and
troubleshooting workflows.
## Changes
- corrected CLI examples in skill docs
- fixed the documented argument order for `performance_analyze_insight`
- updated the memory leak fallback script path
- corrected generated tool reference wording by updating the
source-of-truth tool descriptions
---------
Co-authored-by: ojonesjr <50652264+ojonesjr@users.noreply.github.com>
This PR add a new skill for detecting and removing memory leaks using
take_memory_snapshot tool.
Skill was based on authoritative material from own sources:
* https://developer.chrome.com/docs/devtools/memory-problems
* https://web.dev/articles/effectivemanagement
as well as examples of memory leaks from public domain.
It can be tested with https://github.com/devnook/mem-leak-example.
Example prompt
* A page running at localhost:3000 has memory issues when you click from
home to contact tab and back. Can you fix it?
The skill prefers using comparison tools like memlab instead of custom
evaluate_script snippets to avoid directly reading of .heapsnpashot
files to save context space and tokens.
Fixes#1056
---------
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: Yusheng <113574546+yshngg@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Alex Rudenko <OrKoN@users.noreply.github.com>
Co-authored-by: Mathias Bynens <mathias@qiwi.be>
## Summary
- Fix broken markdown fences in `skills/a11y-debugging/SKILL.md` — a
stray quadruple-backtick on line 72 broke the numbered list
continuation, and a mismatched fence on line 95 disrupted rendering
- Extract verbose JS snippets (orphaned inputs, tap targets, color
contrast, global checks) into `references/a11y-snippets.md`, keeping
SKILL.md scannable and following the same `references/` pattern used by
`debug-optimize-lcp`
## Test plan
- [x] Verify SKILL.md renders correctly in GitHub markdown preview (no
broken fences or orphaned code blocks)
- [x] Verify `references/a11y-snippets.md` renders correctly and all 4
snippets are present
- [x] Confirm the relative links from SKILL.md to
`references/a11y-snippets.md` resolve correctly on GitHub
- **feat: add troubleshooting skill definition and expand documentation
with details on autoConnect timeouts and extension debugging
conflicts.**
- **docs: Simplify troubleshooting skill instructions by removing
explicit tool mentions and updating the troubleshooting guide link.**
- **docs: Update troubleshooting guide to recommend and correct usage of
`--logFile` for capturing debug logs.**
- **docs: Enhance troubleshooting guide with 'Tool not found' error,
`--autoConnect` Chrome 144+ requirement, and `startup_timeout_ms` tip
for Windows.**
- **docs: Clarify that Chrome 144+ must be running for `--autoConnect`
and add a verification step for remote debugging.**
- **feat: Add an initial troubleshooting step to read and interpret MCP
configuration, renumbering subsequent steps.**
- **docs: Add detailed troubleshooting steps for `Could not find
DevToolsActivePort` and other common connection errors.**
- **docs: Add troubleshooting guidance for empty profile creation due to
typos or misconfiguration.**
- **feat: Add Lighthouse audit as the initial step in the accessibility
debugging workflow and reorder subsequent sections.**
- **feat: Add critical instructions for parsing Lighthouse audit reports
to efficiently extract failing elements.**
Added workarounds for using chrome-devtools-mcp in WSL.
Drive-by: moved known issues from readme to troubleshooting.
Drive-by: updated skill to link to troubleshooting.
Drive-by: rephrased for clarity.
mehmet turac