skills.rest
nghiahsgs
nghiahsgsCOMMUNITY
Explore all skills by this author →
GitHub

debug-flight-recorder

Insert marker-based console logs to trace bug execution and revert changes.

32|13|Updated Apr 21, 2026
Search Tags:#debugging#logging#cleanup#instrumentation#reproducible#marker-logs
One-click install
npx skills add https://github.com/nghiahsgs/taw-kit --skill debug-flight-recorder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-flight-recorder
Source: https://github.com/nghiahsgs/taw-kit/tree/main/skills/debug-flight-recorder
Command: npx skills add https://github.com/nghiahsgs/taw-kit --skill debug-flight-recorder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adds contextual, reversible logging around bug call sites so developers can reproduce issues, collect actionable traces, and revert instrumentation without leaving code changes behind.

Core Features & Use Cases

  • Marker-based instrumentation that annotates exact entry points, external calls, and conditional branches
  • Repro-friendly logging workflow: run a repro, gather logs, then automatically clean up
  • Safety & hygiene: scrub sensitive data in logs and ensure complete cleanup after verification

Quick Start

Add marker logs to your code, run a repro, collect the output, then let the tool scrub logs and revert changes.

Frequently Asked Questions about debug-flight-recorder

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

FAQPage Schema
How do I add console logs to trace a bug without leaving permanent changes in my code?▼

To debug without permanent changes, use marker-based instrumentation to insert reversible console logs at entry points and conditionals. This enables reproducible trace collection and safe automated cleanup after verification.

What is marker-based logging and how does it help with debugging?▼

Marker-based logging annotates exact execution paths across entry points, external calls, and conditionals with unique markers. This creates reproducible traces that pinpoint bug call sites while scrubbing sensitive values for safe analysis.

How do I safely add and remove debugging logs around external calls and conditionals?▼

Safely add and remove debugging logs by instrumenting external calls and conditionals with one-line marker logs. After running a repro and collecting output, the tool automatically scrubs logs and reverts instrumentation.

Can I scrub sensitive data from console logs during code instrumentation?▼

Yes, you can scrub sensitive values from console logs during instrumentation. The tool ensures safety and hygiene by scrubbing sensitive data in the generated logs and ensuring complete cleanup after bug verification.

Does this code instrumentation approach work for tracing complex conditional branches?▼

Yes, this instrumentation approach works for tracing complex conditional branches. It applies marker logs across entry points, external calls, and conditionals to capture exact execution paths and enable reproducible debugging.

What is the best way to automatically clean up debugging logs after reproducing an issue?▼

The best way to automatically clean up debugging logs after reproducing an issue is using marker-based instrumentation. After collecting the trace output, the tool automates cleanup to revert all instrumentation safely without leaving code changes behind.

Related Skills

Explore More Software Engineering Skills→
unclecatvnunclecatvn
120

odoo-code-tracer

Trace Odoo execution paths from entry points through method chains.

Community
Advanced
thiagofinchthiagofinch
79

gha

Diagnose the latest GitHub Actions workflow failure using gh CLI logs.

Community
Intermediate
salvo-rssalvo-rs
20

salvo-logging

Capture request metrics, trace spans, and error contexts for Salvo routes.

Official
Intermediate
jvalinskyjvalinsky

objc-log-redaction-audit

Audit Objective-C logging statements for sensitive data exposure.

Community
Intermediate