stacks-browse

Run headless browser QA and SPA navigation checks via Chrome DevTools Protocol.

2|Updated Jul 8, 2026
One-click install
npx skills add https://github.com/bughq/bughq --skill stacks-browse-bughq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stacks-browse
Source: https://github.com/bughq/bughq/tree/main/.claude/skills/stacks-browse
Command: npx skills add https://github.com/bughq/bughq --skill stacks-browse-bughq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the challenge of performing automated quality assurance on Stacks applications without the overhead of heavy dependencies like Playwright or Puppeteer.

Core Features & Use Cases

  • Headless QA: Perform navigation, screenshot capture, and responsive testing using only native Bun capabilities.
  • SPA Verification: Detects whether client-side router transitions are performing fragment swaps or full page reloads, ensuring consistent application state.
  • Accessibility & Monitoring: Audit page structure, accessibility landmarks, and monitor console/network health during automated sessions.

Quick Start

Invoke the stacks-browse skill to navigate to your local application URL and capture a full-page screenshot for visual verification.

Frequently Asked Questions about stacks-browse

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

FAQPage Schema
How do I run headless browser QA on Stacks applications without Playwright or Puppeteer?

You can perform headless browser QA on Stacks applications using this skill, which drives automated testing tasks via the Chrome DevTools Protocol without requiring external npm dependencies like Playwright or Puppeteer.

Can I verify SPA client-side router transitions to check for full page reloads?

Yes, SPA verification detects whether client-side router transitions are performing fragment swaps or full page reloads, ensuring consistent application state during headless browser sessions.

Do I need a specific runtime to automate responsive layout checks and accessibility snapshots?

Yes, you need a local Chromium-family browser and the Bun runtime to drive browser sessions, execute responsive layout checks, and capture accessibility snapshots without external dependencies.

What's the best way to monitor console errors and network health during automated testing?

The best way to monitor console errors and network health is using this skill's automated sessions, which audit page structure, track console output, and verify network stability via the Chrome DevTools Protocol.

How to capture full-page screenshots for visual verification of a local application URL?

Invoke this skill to navigate to your local application URL and capture a full-page screenshot for visual verification, leveraging native Bun capabilities to drive the headless browser session.