Debug, Review, and Q&A in DevTools
Use this skill to:
- Show a target to the user: Open DevTools and reveal a panel, a DOM element, or a network request.
- Inspect the user's selection: Read the element or network request that the user selected in DevTools.
- Address DevTools comments: Fetch comment threads, answer questions or apply fixes, and resolve the threads.
Prerequisites
- Chrome version: Chrome M159 or later.
- Required flag:
--devtools-comments in the MCP server config. Without it, open_devtools, reveal_in_devtools, get_devtools_comments, and resolve_devtools_comment are not available.
- Headed browser: Chrome must not run in
--headless mode.
- Page targeting: All tools require a
pageId from list_pages or new_page.
Workflows
1. Open DevTools
Call open_devtools with pageId. Do this before you call reveal_in_devtools, get_devtools_comments, or resolve_devtools_comment.
2. Reveal a panel, element, or network request
Call reveal_in_devtools with pageId and these optional parameters:
panelName: "elements", "network", "sources", or "console". Pass it alone to switch panels.
uid: Element uid from take_snapshot. Reveals the element in the Elements panel.
reqid: Request reqid from list_network_requests. Reveals the request in the Network panel.
uid and reqid are mutually exclusive.
3. Inspect the user's selection
- DOM element: Call
take_snapshot. The snapshot marks the element selected in the Elements panel. Pass its uid to get_css_styles, take_screenshot, or evaluate_script.
- Network request: Call
get_network_request and omit reqid. It returns the request selected in the Network panel.
4. Handle comment threads
Select the mode from the user's request.
Mode A: One-shot (comments already exist)
Use this mode when the user says the comments are already in DevTools, or asks you not to poll.
- Call
get_devtools_comments once.
- Process and resolve each returned thread.
- Summarize your changes and answers in chat, then end your turn. Do not poll.
Mode B: Watch (wait for user feedback)
Use this mode when the user asks you to wait while they debug, review, or add comments.
- Call
get_devtools_comments immediately.
- While the result is
"No open DevTools comments found.", wait 10 seconds, then call it again. Call it immediately if a "DevTools comment threads updated" notification arrives.
- Stop after 12 consecutive empty polls (about 2 minutes) or when the user asks you to stop.
- When threads appear, process and resolve them. Then reset the empty-poll counter and continue polling.
Rules for polling:
- Use a background sub-agent when sub-agent tools are available, so the main thread stays responsive. The sub-agent returns the threads to the main agent, or resolves them itself if it has workspace and MCP tools.
- Poll inline only when sub-agent tools are unavailable. Do not end your turn early.
- Never call
get_devtools_comments back-to-back without the 10-second delay.
Process and resolve a thread
For each ### Thread: <id>:
- Inspect the anchored target:
Related element uid: Use get_css_styles, take_snapshot, or take_screenshot with the uid.
Related network reqid: Use get_network_request with the reqid.
- Optionally call
reveal_in_devtools to show the target to the user.
- Address the comment:
- For a code or styling request, apply the fix in the workspace. Reload and verify the page if needed.
- For a question or root-cause investigation, collect diagnostic data. Do not make unnecessary code edits.
- Resolve: Call
resolve_devtools_comment with pageId, threadId, and replyText:
- For a question or root cause, write a detailed answer.
- For a straightforward fix, write 1–2 sentences that state the change and the file.
1---2name: inspect-in-devtools3description: Use this skill to connect to the Chrome DevTools UI for interactive debugging, UI/UX review, Q&A, showing elements/network requests/panels to the user, inspecting the user's current DevTools selection, and addressing or polling for DevTools UI comment threads.4metadata:5 source: https://skillmd.com/skills/gabrielmoreira/inspect-in-devtools6---78# Debug, Review, and Q&A in DevTools910Use this skill to:11121. **Show a target to the user**: Open DevTools and reveal a panel, a DOM element, or a network request.132. **Inspect the user's selection**: Read the element or network request that the user selected in DevTools.143. **Address DevTools comments**: Fetch comment threads, answer questions or apply fixes, and resolve the threads.1516## Prerequisites1718- **Chrome version**: Chrome M159 or later.19- **Required flag**: `--devtools-comments` in the MCP server config. Without it, `open_devtools`, `reveal_in_devtools`, `get_devtools_comments`, and `resolve_devtools_comment` are not available.20- **Headed browser**: Chrome must not run in `--headless` mode.21- **Page targeting**: All tools require a `pageId` from `list_pages` or `new_page`.2223## Workflows2425### 1. Open DevTools2627Call `open_devtools` with `pageId`. Do this before you call `reveal_in_devtools`, `get_devtools_comments`, or `resolve_devtools_comment`.2829### 2. Reveal a panel, element, or network request3031Call `reveal_in_devtools` with `pageId` and these optional parameters:3233- `panelName`: `"elements"`, `"network"`, `"sources"`, or `"console"`. Pass it alone to switch panels.34- `uid`: Element `uid` from `take_snapshot`. Reveals the element in the Elements panel.35- `reqid`: Request `reqid` from `list_network_requests`. Reveals the request in the Network panel.3637`uid` and `reqid` are mutually exclusive.3839### 3. Inspect the user's selection4041- **DOM element**: Call `take_snapshot`. The snapshot marks the element selected in the Elements panel. Pass its `uid` to `get_css_styles`, `take_screenshot`, or `evaluate_script`.42- **Network request**: Call `get_network_request` and omit `reqid`. It returns the request selected in the Network panel.4344### 4. Handle comment threads4546Select the mode from the user's request.4748#### Mode A: One-shot (comments already exist)4950Use this mode when the user says the comments are already in DevTools, or asks you not to poll.51521. Call `get_devtools_comments` once.532. Process and resolve each returned thread.543. Summarize your changes and answers in chat, then end your turn. Do **not** poll.5556#### Mode B: Watch (wait for user feedback)5758Use this mode when the user asks you to wait while they debug, review, or add comments.59601. Call `get_devtools_comments` immediately.612. While the result is `"No open DevTools comments found."`, wait 10 seconds, then call it again. Call it immediately if a `"DevTools comment threads updated"` notification arrives.623. Stop after 12 consecutive empty polls (about 2 minutes) or when the user asks you to stop.634. When threads appear, process and resolve them. Then reset the empty-poll counter and continue polling.6465Rules for polling:6667- **Use a background sub-agent** when sub-agent tools are available, so the main thread stays responsive. The sub-agent returns the threads to the main agent, or resolves them itself if it has workspace and MCP tools.68- **Poll inline** only when sub-agent tools are unavailable. Do not end your turn early.69- **Never call `get_devtools_comments` back-to-back** without the 10-second delay.7071#### Process and resolve a thread7273For each `### Thread: <id>`:74751. **Inspect the anchored target**:76 - `Related element uid`: Use `get_css_styles`, `take_snapshot`, or `take_screenshot` with the `uid`.77 - `Related network reqid`: Use `get_network_request` with the `reqid`.78 - Optionally call `reveal_in_devtools` to show the target to the user.792. **Address the comment**:80 - For a code or styling request, apply the fix in the workspace. Reload and verify the page if needed.81 - For a question or root-cause investigation, collect diagnostic data. Do not make unnecessary code edits.823. **Resolve**: Call `resolve_devtools_comment` with `pageId`, `threadId`, and `replyText`:83 - For a question or root cause, write a detailed answer.84 - For a straightforward fix, write 1–2 sentences that state the change and the file.