repro-admin

Reproduce an EmDash admin UI bug with screenshots and a replayable transcript.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reproduce an EmDash admin UI bug in a controlled demo to verify symptoms, gather artifacts, and document a reproducible sequence.

Core Features & Use Cases

  • Boots a demo with bgproc and runs the dev server for an EmDash admin UI repro.
  • Drives the admin using an automated browser (agent-browser) to replay the reporter steps.
  • Captures screenshots and a precise transcript to support bug verification and regression testing.

Quick Start

Boot the demo with bgproc and drive the admin UI with agent-browser to reproduce the reporter's steps and collect screenshots and a transcript.

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 reliably in a demo environment?

To reproduce an admin UI bug reliably, boot a demo using bgproc, authenticate a dev-bypass session, and drive the UI with agent-browser to capture screenshots and a replayable transcript of the steps.

Can I use an automated browser to capture screenshots and a transcript for bug triage?

Yes, you can use an automated browser to capture screenshots and a precise transcript for bug triage by driving the admin UI through the reporter steps and recording the interaction sequence.

Do I need a running demo and an authenticated session to verify admin UI regressions?

Yes, verifying admin UI regressions requires a running demo booted via bgproc and an authenticated dev-bypass session to exercise the admin interface and reproduce the bug symptoms.

What's the best way to document a reproducible sequence for an admin UI bug?

The best way to document a reproducible sequence is to drive the admin UI with an automated browser, capturing a replayable transcript and screenshots that record the exact steps triggering the bug.

When do I need a replayable transcript for QA workflows?

You need a replayable transcript for QA workflows during bug triage and regression verification to capture a durable reproduction artifact that precisely documents the UI interaction steps taken.