inspect-browser-console-errors
Inspect browser console errors by preserving page, version, action, source, stack, network, and reproduction context. Use when a web page logs exceptions, warnings, policy failures, or rejected resources.
来源信息
- 仓库
- protosphinx/sphinxstack
- 最近来源活动
- 2026年7月29日 13:55
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 3
- Forks
- 0
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
2 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- inspect-browser-console-errors
- category
- web
- description
- Inspect browser console errors by preserving page, version, action, source, stack, network, and reproduction context. Use when a web page logs exceptions, warnings, policy failures, or rejected resources.
# inspect-browser-console-errors
Treat console output as evidence, not a root cause.
## When to use
- Use for page-load, interaction, extension, security-policy, resource, or script failures.
- Do not expose tokens, cookies, personal data, private URLs, or production source maps.
## Procedure
1. Record URL, environment, browser and version, device, user state, build, time, and exact action.
2. Preserve complete messages, levels, stacks, source locations, grouping, and timestamps.
3. Separate application, browser, extension, network, policy, deprecation, and third-party output.
4. Correlate with failed requests, response headers, request IDs, and server logs.
5. Reproduce in a clean profile and another browser or known-good version.
6. Map the first application-controlled failure to the exact deployed source.
7. Form and test one discriminating hypothesis at a time.
8. Save a redacted diagnostic report.
## Done
- A console diagnostic report records context, errors, sources, network correlations, and deployed version
- Clean reproduction and a focused test confirm or reject the identified application-controlled cause
在 GitHub 查看