repro-api

Reproduce backend bugs as deterministic local failures with vitest regression tests.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ahliweb/sikesra --skill repro-api-ahliweb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repro-api
Source: https://github.com/ahliweb/sikesra/tree/main/awcmsmicro-dev/.flue/skills/repro-api
Command: npx skills add https://github.com/ahliweb/sikesra --skill repro-api-ahliweb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a reported backend issue into a deterministic local reproduction, so you can confirm the exact failure mode before attempting a fix.

Core Features & Use Cases

  • Focused Bug Reproduction: Targets REST handlers, CLI behavior, MCP flows, migrations, schema registry logic, and build tooling.
  • Regression-Ready Output: Prefers a failing vitest test that can remain in place as a permanent guardrail after the bug is fixed.
  • Evidence Capture: Records the exact command, meaningful output, and exit code so the failure can be reviewed and shared confidently.

Quick Start

Ask for a deterministic local reproduction of the reported backend bug and specify the affected package, command, or stack trace.

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 backend bug as a failing vitest test?

A deterministic local reproduction turns a reported backend issue into a failing vitest test or reproducible script. It captures exact command output, stderr, and exit code to confirm the failure mode before attempting a fix.

What is the best way to create a regression test for REST handler bugs?

Creating a regression test for REST handler bugs involves generating a deterministic local failure with captured stdout, stderr, and exit code. The Skill outputs a failing vitest test that remains as a permanent guardrail after the bug is fixed.

Can I reproduce CLI command failures locally with captured stdout and exit codes?

Yes, reproducing CLI command failures locally captures stdout, stderr, and exit code in a single command or script. The Skill targets CLI behavior and build tooling to produce deterministic local failures for review.

Does this approach work for reproducing database migration and schema registry issues?

Yes, reproducing migration and schema registry issues is supported. The Skill covers migrations and schema registry logic in local environments, generating deterministic failures or reproducible scripts to confirm the exact issue.

How do I capture MCP server bugs as a deterministic local failure?

Capturing MCP server bugs as a deterministic local failure involves specifying the affected MCP flows. The Skill outputs a failing vitest test or reproducible script with captured output and exit code to confirm the exact failure mode.

What do I need to start reproducing backend issues with a regression test?

Starting a backend issue reproduction requires the reported issue details and the affected package, command, or stack trace. The Skill uses these inputs to generate a deterministic local failure and a failing vitest regression test.