skills.rest
emdash-cms
emdash-cmsOFFICIAL
Explore all skills by this author →
GitHub

repro-api

Reproduce EmDash bugs below the browser layer with failing vitest tests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reproducing EmDash bugs that live below the browser layer can be difficult and time-consuming; this Skill provides a structured, local workflow to generate repeatable failures.

Core Features & Use Cases

  • Structured reproduction guidance for REST handlers, CLI, migrations, MCP, schema registry, and build tooling.
  • Regression fixture generation by encouraging a failing vitest test to serve as the regression artifact.
  • Safe, documented steps that avoid browser involvement and external side effects.

Quick Start

Run the reproducibility guide locally by creating a failing vitest test in the affected package and running the test suite.

Frequently Asked Questions about repro-api

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

FAQPage Schema
How do I reproduce a REST handler or CLI bug locally without using the browser?▼

To reproduce a bug locally without the browser, identify the affected package, install dependencies if needed, and capture a failing vitest test to serve as a deterministic regression fixture for the non-browser code path.

What is the best way to create a regression fixture for an EmDash migration or schema registry issue?▼

The best way to create a regression fixture for an EmDash migration or schema registry issue is to write a failing vitest test in the affected package that deterministically reproduces the exact failure locally.

Can I use vitest to test EmDash MCP and build tooling code paths?▼

Yes, you can use vitest to test EmDash MCP and build tooling code paths by generating a failing test within the affected package to capture and reproduce the specific non-browser issue locally.

How do I document the exact steps to reproduce a non-browser EmDash bug?▼

Document the exact steps to reproduce a non-browser EmDash bug by identifying the affected package, ensuring dependencies are installed, and recording the failing vitest test alongside the structured reproduction guidance.

Why should I avoid browser involvement when reproducing REST handler or CLI failures?▼

Avoiding browser involvement when reproducing REST handler or CLI failures ensures safe, documented steps that prevent external side effects and enable deterministic local reproduction of the underlying code path issue.

Related Skills

Explore More Software Engineering Skills→
adbutterfieldadbutterfield

running-vitest-safely

Run Vitest test suites with --run, timeouts, and preflight checks.

Community
Advanced
mandersogitmandersogit

debugging

Debug Python code by reproducing issues, analyzing logs, and verifying fixes.

Community
Basic
Jonathan0823Jonathan0823
7

bug-fixing

Reproduce bugs, analyze root causes, implement fixes, and verify with regression tests.

Community
Basic
tgmarinhotgmarinho

diagnosing-bugs

Construct feedback loops to diagnose hard-to-reproduce bugs and performance regressions.

Community
Advanced