browser

Reproduce browser-based bugs and collect screenshots, console errors, and network traces.

Updated Aug 23, 2026

Search Tags:#screenshots #evidence #e2e-testing #browser #bug-reproduction #console-logs #network-tracing

Ready to run

npx skills add https://github.com/CuongTran69/tramthientra --skill browser-cuongtran69

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browser
Source: https://github.com/CuongTran69/tramthientra/tree/main/.augment/skills/browser
Command: npx skills add https://github.com/CuongTran69/tramthientra --skill browser-cuongtran69

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables you to reproduce bugs and explore app behavior directly in a browser, collecting screenshots, console errors, and network traces to support root-cause analysis.

Core Features & Use Cases

End-to-end diagnostics: drive the app as a user would, observe UI behavior, and capture evidence at each step.
Evidence-first reporting: attach screenshots, console logs, and network activity to support findings.
Codebase-aware debugging: map browser observations to source code to identify root causes.

Quick Start

Reproduce the issue in the app using the browser to gather evidence and guide the fix.

Frequently Asked Questions about browser

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I reproduce a browser bug and collect evidence like console logs and network traces?▼

To reproduce a browser bug and collect evidence, you drive the application as a user would to observe UI behavior, capturing screenshots, console errors, and network activity at each step to support root-cause analysis.

What is the best way to capture network traces and screenshots during exploratory UI testing?▼

During exploratory UI testing, the best way to capture network traces and screenshots is by driving the web app directly in a local dev-browser to gather evidence and guide the fix with visual verification.

Do I need a local dev-browser to reproduce bugs and diagnose UI issues?▼

Yes, reproducing browser-based bugs and diagnosing UI issues requires a local dev-browser tool, access to the app URL, and codebase mapping to effectively correlate collected evidence with the source code.

How does codebase-aware debugging help with bug reproduction in web apps?▼

Codebase-aware debugging helps with bug reproduction in web apps by mapping browser observations, such as console errors and network traces, directly to the source code to identify the root cause of UI issues.

Can I use this approach for end-to-end diagnostics and visual verification across web apps?▼

Yes, you can use this approach for end-to-end diagnostics and visual verification across web apps by driving the UI as a user would, observing behavior, and attaching evidence-first reports with screenshots and logs.