repro-admin

Reproduce EmDash admin UI bugs by driving a headless browser and capturing screenshots.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Confirming a reported admin UI bug requires a running demo, an authenticated session, and a repeatable way to drive the interface. This Skill automates that reproduction workflow so a maintainer gets verified evidence instead of unverified guesses. ## Core Features & Use Cases - Automated demo boot: Starts the EmDash demo dev server with bgproc and waits for the port to open before proceeding. - Authenticated browser driving: Uses the dev-bypass endpoint to create a session, then drives the React admin through agent-browser with accessibility-tree refs. - Evidence capture: Takes screenshots at meaningful steps, monitors console and runtime errors, and produces a replayable transcript of the exact reproduction steps. - Use Case: A GitHub issue reports that saving a collection item in the admin shows a blank panel. Use this Skill to boot the demo, follow the reporter's steps in a headless browser, confirm the broken state, and return screenshots plus a step-by-step transcript. ## Quick Start Reproduce the admin UI bug described in this issue by booting the demo, driving the admin with agent-browser, and capturing screenshots of the broken state.

Frequently Asked Questions about repro-admin

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

FAQPage Schema
How do I reproduce an admin UI bug in a headless browser?

Boot the demo dev server with bgproc, open the dev-bypass endpoint to get an authenticated session, then drive the UI with agent-browser using snapshot refs for clicks and form fills. Capture screenshots at each meaningful step and record the exact replayable sequence.

How to get an authenticated admin session for local testing?

Open the /_emdash/api/setup/dev-bypass endpoint on localhost:4321, which runs migrations, creates a dev admin user, sets a session cookie, and redirects to the admin home. It only exists in dev mode and cannot be used against deployed environments.

Can this reproduce browser-specific or OS-level bugs?

No. Bugs requiring a specific browser engine like Safari, OS-level interactions such as native file pickers or IME flows, real browser extensions, or Cloudflare Access in front of the admin cannot be reproduced and should be marked skipped with a reason.

Why does the reproduction fail before reaching the admin page?

If the dev server never opens a port, inspect bgproc logs and treat it as a setup failure rather than a reproduction. Only failures observed after successfully driving the UI count as confirmed bug reproductions.

Should I write a Playwright test to confirm the bug?

No. The workflow explicitly prohibits writing Playwright or other test code because the bot cannot reliably run it, making an unrun test unverified guesswork. Regression tests belong to whoever lands the fix.