reproduce

Instrument code to POST JSON logs to a local clog server on port 2999.

7|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/ferrucc-io/clog --skill reproduce-ferrucc-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reproduce
Source: https://github.com/ferrucc-io/clog/tree/main/.claude/skills/reproduce
Command: npx skills add https://github.com/ferrucc-io/clog --skill reproduce-ferrucc-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow helps developers debug bugs by instrumenting code with clog log statements that POST structured logs to a local server, enabling efficient root-cause analysis without manual log collection.

Core Features & Use Cases

  • Instrumentation: insert lightweight logging calls that POST JSON to the clog server to capture execution traces during bug reproduction.
  • Reproduction workflow: guide users to reproduce the bug while logs highlight divergences between expected and actual behavior.
  • Cross-language applicability: works with Python, JavaScript/Node, Rust, and shell codebases to centralize logs for analysis.

Quick Start

Install clog, start the server on port 2999, and begin instrumenting your code to emit clog logs for reproduction.

Frequently Asked Questions about reproduce

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

FAQPage Schema
How do I add structured logging to trace a bug during reproduction?

To trace a bug during reproduction, you instrument code with lightweight logging calls that POST JSON to a local clog server, capturing execution traces for root-cause analysis. This structured logging highlights divergences between expected and actual behavior without manual log collection.

Can I use this structured logging workflow across different programming languages?

Yes, this structured logging workflow works across Python, JavaScript/Node, Rust, and shell codebases. It centralizes logs by inserting language-agnostic POST requests to a local server, allowing you to analyze cross-language execution traces during bug reproduction.

What's the best way to debug state and timing issues with traceable logs?

The best way to debug state, timing, and data-flow issues is to instrument your code with traceable logs that POST JSON to a local server. Analyzing the resulting ndjson logs locates the root cause by highlighting execution divergences during reproduction.

Do I need a specific port or server setup to capture structured execution traces?

Yes, you need to install clog and start the server on port 2999. Once running, insert logging calls that POST JSON to the /log endpoint, which captures structured execution traces locally for analysis.

How does posting JSON logs to a local server help with root-cause analysis?

Posting JSON logs to a local server helps with root-cause analysis by centralizing execution traces in ndjson format. This eliminates manual log collection, allowing you to efficiently compare expected and actual behavior to pinpoint the exact source of the bug.