メニュー
Use when verifying browser-based behaviour with Chrome DevTools, including DOM state, console output, network activity and performance evidence.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when reviewing code before merge to assess correctness, tests, maintainability, security and user impact.
Use when reviewing plans, recommendations, prioritisation, risk registers, retrospectives or agent outputs for judgement distortion from cognitive bias — not for checking whether an argument's premises validly support its conclusion.
Use when evaluating whether premises in plans, ADRs, reviews, security justifications or agent recommendations validly support their conclusions — for logical fallacies, not judgement distortion from cognitive bias.
Use when a coding agent needs robust problem solving, explicit decomposition, alternative-path exploration, program-aided reasoning, ReAct loops, or self-correction.
Use when generated code, plans, tests, prompts or architecture need critique, repair and verification before completion; especially for coding tasks requiring self-review, test-driven repair or quality gates.
Identifies risks, scores likelihood and impact, selects treatment, assigns owners and review cadence. Use when building or updating a risk register, treating agent autonomy risks, or deciding mitigate, transfer, accept or avoid.
| name | browser-testing-with-devtools |
| description | Use when verifying browser-based behaviour with Chrome DevTools, including DOM state, console output, network activity and performance evidence. |
| aliases | ["browser-debugging","chrome-devtools-testing"] |
Use this skill when a change affects a browser-rendered interface and you need runtime evidence from the browser rather than static code inspection alone.
Verify user-facing behaviour with DevTools evidence so frontend or browser issues are reproduced, localized and confirmed with the actual runtime state.
