repro-api

What problem does it solve? Bug reports for server-side code often lack a deterministic reproduction, making diagnosis slow and error-prone. This Skill turns an issue report about EmDash's REST handlers, CLI, MCP server, migrations, schema registry, or build tooling into a concrete, repeatable failure the team can act on. ## Core Features & Use Cases - Failing vitest tests: Writes a reproduction test in the affected package's tests directory, using shared test database utilities, so it becomes the regression fixture after the fix. - Fallback reproduction paths: Falls back to a standalone repro script under /tmp or a direct pnpm CLI invocation when a test would require too much scaffolding. - Skip criteria: Recognizes non-reproducible cases such as deployed Worker behavior, production-scale Postgres issues, missing customer artifacts, and timing-dependent heisenbugs, and reports them instead of wasting runner time. - Use Case: A user reports that an EmDash REST handler returns the wrong status code. The Skill locates the handler in packages/core/src/api/handlers/, writes a failing vitest test mirroring the source structure, confirms it fails for the reported reason, and records the exact command and output for the diagnosis stage. ## Quick Start Reproduce the bug described in this EmDash issue by writing a failing vitest test in the affected package and report the exact command and failure output.