repro-public

Reproduce public-site bugs in an Astro demo using browser automation and screenshots.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/Thigh-Food/emdash --skill repro-public-thigh-food
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repro-public
Source: https://github.com/Thigh-Food/emdash/tree/main/.flue/skills/repro-public
Command: npx skills add https://github.com/Thigh-Food/emdash --skill repro-public-thigh-food

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Confirming a reported bug on the public-facing rendered site is slow and error-prone when done by hand, and unverified reproductions waste maintainer time. This Skill boots a local EmDash demo, drives the public routes with a browser agent, and produces a replayable transcript with screenshots as durable evidence. ## Core Features & Use Cases - Guided reproduction workflow: Re-reads the issue, picks an appropriate demo, seeds content via the EmDash CLI, and starts the dev server on localhost:4321. - Browser-driven verification: Uses agent-browser to open affected routes, inspect the accessibility tree, capture console and runtime errors, and take screenshots at meaningful states. - Structured output: Returns whether the bug was reproduced, skip reasons when reproduction is impossible, and a precise step-by-step transcript with artifact paths. - Use Case: A reporter files an issue that the RSS feed returns broken markup for a specific locale. You select a multi-locale demo, open the feed URL in the browser, capture the malformed output, and hand maintainers an exact replayable sequence. ## Quick Start Reproduce the public-site bug described in this issue by booting the demo and driving the affected route with agent-browser, then report screenshots and replayable steps.

Frequently Asked Questions about repro-public

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

FAQPage Schema
How do I reproduce a bug on a public Astro site?

Start the demo dev server with bgproc, open the exact affected route on localhost:4321 using agent-browser, and inspect the rendered output via the accessibility tree and console logs. Capture screenshots at each meaningful state and record the replayable steps.

How do I seed content for bug reproduction in EmDash?

Use the EmDash CLI command pnpm exec emdash content create with the collection name and data payload to create ephemeral content. Avoid editing seed files, since CLI-created content disappears with the workspace.

Can I write Playwright tests to confirm a public-site bug?

No. This workflow explicitly prohibits writing Playwright or other automated tests because they cannot be reliably run in the environment. The durable artifacts are screenshots, a captured DOM slice, and a written transcript instead.

When should a public-site bug reproduction be skipped?

Skip when the bug requires third-party fetchers like crawler user-agents, production-scale content such as sitemap chunking, deployed Worker behavior like edge caching, or source datasets the reporter did not attach.

Why does my reproduction not match the reported bug symptoms?

Rendering differences often come from missing seed data, cached build artifacts, or unrelated routes. Verify the exact URL, query string, and Accept header from the issue, and note the mismatch explicitly if the symptom cannot be produced.