skills.rest
reliant-labs
reliant-labsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

reproduce

Reproduce software bugs with diagnostic logging and minimal e2e triggers.

4|1|Updated Apr 12, 2026
Search Tags:#debugging#developer workflow#e2e testing#bug reproduction#runtime evidence#diagnostic logging#service logs
One-click install
npx skills add https://github.com/reliant-labs/forge --skill reproduce-reliant-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reproduce
Source: https://github.com/reliant-labs/forge/tree/main/internal/templates/project/skills/forge/debug/reproduce
Command: npx skills add https://github.com/reliant-labs/forge --skill reproduce-reliant-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reproduce bugs that cannot be diagnosed through code reading by gathering concrete runtime evidence, pinpointing the failing paths, and producing repeatable e2e triggers.

Core Features & Use Cases

  • Diagnostic logging with cleanup markers: Add clearly labeled debug logs that capture inputs, state changes, branch decisions, wrapped errors, and final outputs without leaving noise after the fix.
  • Targeted triggering and attachment: Trigger the bug directly (e.g., via API calls) and use runtime tooling like a debugger attachment when logs alone are insufficient.
  • Minimal end-to-end reproduction: Create a small e2e test that first asserts the wrong behavior, then flips to the expected behavior once fixed.

Quick Start

Ask your team to run the failing service, identify the relevant route and handler, add DEBUG-REPRO logging around inputs/state/branches/errors, then write a minimal e2e test that reproduces the wrong behavior against the live stack.

Frequently Asked Questions about reproduce

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

FAQPage Schema
How do I reproduce a software bug using runtime evidence and service logs?▼

To reproduce a software bug using runtime evidence, you collect structured diagnostic logging and repeatable end-to-end triggers. This involves identifying the failing handler via service logs and proto route definitions, then validating the issue with a minimal test against the live stack.

What's the best way to add diagnostic logging for bug reproduction without leaving debug noise?▼

The best way to add diagnostic logging for bug reproduction is to use clearly labeled DEBUG-REPRO markers. This captures inputs, state changes, branch decisions, and wrapped errors during debugging, allowing you to easily find and clean up the debug logs after applying your fix.

How do I create a minimal e2e test that reproduces a bug against a live stack?▼

To create a minimal e2e test that reproduces a bug against a live stack, you trigger the failing behavior directly via API calls. You first write a test asserting the wrong behavior, then flip it to assert the expected behavior once the code is fixed.

When do I need to attach a debugger for service debugging instead of just reading code?▼

You need to attach a debugger for service debugging when logs alone are insufficient and code reading cannot diagnose the issue. Use targeted commands to attach a debugger to the failing handler after capturing the environment and observed-versus-expected behavior.

Can I trigger bug reproduction directly through API calls for e2e testing?▼

Yes, you can trigger bug reproduction directly through API calls for e2e testing. By applying targeted triggering to the live stack, you can reproduce the exact failing behavior and validate it using a minimal end-to-end test.

Why should I capture environment and observed-versus-expected behavior for bug reproduction?▼

Capturing environment and observed-versus-expected behavior is required for bug reproduction to pinpoint failing paths accurately. This runtime evidence ensures you identify the correct proto route definitions and handler before adding DEBUG-REPRO logging or writing validation tests.

Related Skills

Explore More Software Engineering Skills→
NotysotyNotysoty
9

Bug Root Cause Analyzer

Trace stack traces and generate structured root-cause reports for software bugs.

Community
Advanced
logo-solutionslogo-solutions

debugging-and-error-recovery

Guide systematic root-cause debugging of failing tests and build errors.

Official
Advanced
SethyPagnaSethyPagna

python-debugpy

Attach interactive debuggers to Python processes for breakpoint-driven tracing.

Community
Advanced
jshsakurajshsakura
22

debugger

Isolate software bug root causes across code paths using evidence-driven analysis.

Community
Advanced