repro-public

Reproduce public-site rendering bugs via bgproc demo and agent-browser.

11.6k|1.1k|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/emdash-cms/emdash --skill repro-public
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repro-public
Source: https://github.com/emdash-cms/emdash/tree/main/.flue/skills/repro-public
Command: npx skills add https://github.com/emdash-cms/emdash --skill repro-public

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reproduce public-site rendering bugs by booting a controlled demo and capturing evidence to verify and communicate failures.

Core Features & Use Cases

  • Boot a deterministic demo with bgproc to isolate an issue on the public site.
  • Drive public routes with agent-browser to observe SSR output, public routing, sitemap, RSS, and image rendering from a visitor perspective.
  • Produce durable artifacts: screenshots, a replayable transcript, and a concise written report for regression tracking.

Quick Start

Boot the demo with bgproc, then drive public routes with agent-browser to reproduce the issue and generate screenshots plus a transcript.

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-facing website without an admin session?▼

To reproduce a public-site bug without an admin session, boot a deterministic demo via bgproc and drive public routes with agent-browser to capture screenshots and a written transcript as evidence.

What is the best way to capture evidence of SSR rendering bugs for regression tracking?▼

Capturing SSR rendering bugs for regression tracking involves driving public routes with agent-browser to generate durable artifacts, including screenshots and a replayable transcript that verify the rendering failure.

Can I test sitemap, RSS, and image rendering issues from a visitor's perspective?▼

Yes, you can test sitemap, RSS, and image rendering issues from a visitor's perspective by driving public routes outside the admin session with agent-browser to observe the SSR output.

How do I isolate a public routing bug using a controlled demo environment?▼

You isolate a public routing bug by booting a controlled demo with bgproc, which creates a deterministic environment to safely reproduce the issue and capture the exact routing failure.

What durable artifacts are produced when reproducing public-site bugs?▼

Reproducing public-site bugs produces durable artifacts including screenshots, a replayable transcript, and a concise written report to verify failures and communicate the rendering issues for regression tracking.