About w-debug-browser
A Basilic workflow skill for investigating browser-visible failures, applying a minimal authorized fix, and verifying it by replaying the interaction. It emphasizes collecting runtime evidence and distinguishing it from automated test results.
Key features
- 01Reproduce the affected browser interaction
- 02Collect DOM, network, and console evidence
- 03Trace the owning client or server boundary
- 04Replay the interaction after a fix
- 05Run affected automated checks
Use cases
- 01Investigate a broken browser interaction
- 02Diagnose failures or empty states with runtime evidence
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ blockmatic-icebox/ basilic-skills --skill w-debug-browserAfter installing, type/w-debug-browserin Claude Code to confirm it loaded.
Details
From the project READMEUse the affected URL, expected interaction, and available browser tools. Inspect the app's README and browser-testing conventions first.
- Reproduce the interaction and collect relevant DOM, network, and console evidence before adding instrumentation.
- Trace the failure to its owning client or server boundary. Use the repository logger for necessary temporary traces; avoid secrets in captured output.
- Apply the smallest authorized fix, then replay the same interaction and relevant failure or empty states.
- Run affected automated checks and remove temporary traces introduced here. Distinguish runtime evidence from automated results. If tools or credentials block reproduction, report the exact limitation rather than looping without new evidence.
- Docs:
/w-docsif behavior or commands changed.
Comments
Markdown supported