capture-repro

Creates deterministic capture baselines and environment snapshots for runtime debugging.

15|5|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/haolange/RDC-Agent-Frameworks --skill capture-repro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capture-repro
Source: https://github.com/haolange/RDC-Agent-Frameworks/tree/main/debugger/platforms/claude-code/.claude/skills/capture-repro
Command: npx skills add https://github.com/haolange/RDC-Agent-Frameworks --skill capture-repro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill formalizes the creation of reproducible capture baselines and anchors to enable safe, verifiable live debugging and postmortem analysis without bypassing broker controls or leaking runtime handles.

Core Features & Use Cases

  • Deterministic Capture Baselines: Define and record reproducible capture steps and artifacts that allow precise reruns of problematic runtime states.
  • Broker-mediated Safety: Enforce staged handoff, broker ownership, and single-runtime policies so specialists never directly hold or misuse live tooling.
  • Use Case: When rdc-debugger dispatches a specialist for a flaky or failing runtime case, use this Skill to generate intake artifacts, environment snapshots, and reproducible reproduction steps stored under the platform-local workspace.

Quick Start

Ask rdc-debugger to dispatch capture-repro to create a reproducible capture baseline for the failing runtime case and write required artifacts into the platform-local workspace.

Frequently Asked Questions about capture-repro

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

FAQPage Schema
How do I create a reproducible capture baseline for runtime debugging?

To create a reproducible capture baseline for runtime debugging, you generate deterministic capture steps, intake artifacts, and environment snapshots. This ensures you can precisely rerun problematic runtime states for safe live investigation and postmortem analysis.

What are intake artifacts in a staged handoff debugging workflow?

Intake artifacts in a staged handoff debugging workflow are structured records, specifically the required intake_gate.yaml file. They define deterministic capture steps and environment snapshots to securely transfer runtime context without leaking handles.

Can I directly hold live runtime tools during incident reproduction?

No, you cannot directly hold live runtime tools during incident reproduction. Broker-mediated tool ownership enforces staged handoffs and single-runtime single-context policies to prevent specialists from misusing live tooling.

How do I take an environment snapshot for postmortem analysis?

You take an environment snapshot for postmortem analysis by dispatching a capture workflow to produce deterministic capture steps. These steps and required broker artifacts are written into the platform-local workspace.

Do I need a broker to establish reproducible capture anchors?

Yes, you need a broker to establish reproducible capture anchors. Broker-mediated safety requires complete runtime broker artifacts and adherence to single-runtime single-context policies to prevent bypassing controls during live debugging.