debugging

Name: debugging
Availability: InStock
Author: willchangethislater

Automates reproducible debugging workflows with evidence capture across multiple tools.

1|Updated Sep 10, 2024

Search Tags:#debugging #troubleshooting #tmux #mitmproxy #rpdb #convo #debugging-playbook

Ready to run

npx skills add https://github.com/WillChangeThisLater/dotfiles --skill debugging-willchangethislater

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/WillChangeThisLater/dotfiles/tree/main/pi/.pi/agent/skills/pi-skills/debugging
Command: npx skills add https://github.com/WillChangeThisLater/dotfiles --skill debugging-willchangethislater

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides repeatable debugging patterns and tooling guidance to quickly isolate and diagnose tricky issues in complex environments, reducing guesswork and time to resolution.

Core Features & Use Cases

Repeatable techniques: tmux-based pane instrumentation, traffic inspection with mitmproxy, remote debugging with rpdb, and conversational pane assistance for quick log understanding.
Structured workflows: documented steps that capture evidence, timestamps, and reproducible repros to enable fast comprehension and handoffs.
Use Case: When a bug is hard to reproduce, apply this Skill to instrument, observe, and collect traces across tools to locate the root cause.

Quick Start

Start a debugging session by invoking the recommended tooling and following the predefined reproducible steps to capture evidence.

Frequently Asked Questions about debugging

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

FAQPage Schema

How do I debug tricky issues that are hard to reproduce in complex environments?▼

To debug tricky issues that are hard to reproduce, apply repeatable patterns using tmux, mitmproxy, and rpdb to instrument, observe, and collect traces. This isolates the root cause through deterministic steps and evidence capture.

What is the best way to capture evidence during a troubleshooting session?▼

The best way to capture evidence during troubleshooting is to follow structured workflows that document reproducible steps, record timestamps, and collect traces. This enables fast comprehension and structured handoffs for later review.

How does mitmproxy work with tmux for traffic inspection?▼

Mitmproxy works with tmux by using tmux-based pane instrumentation to inspect traffic alongside other debugging tools. This allows you to observe network requests and interactively inspect logs within a single structured session.

Can I use rpdb for remote debugging in my development sessions?▼

Yes, you can use rpdb for remote debugging in your development sessions. It is integrated as a repeatable technique to provide interactive inspection capabilities across complex environments during tricky issue isolation.

Do I need convo to understand logs during interactive inspection?▼

You can use convo for conversational pane assistance to achieve quick log understanding during interactive inspection. It helps parse and interpret the evidence captured within your debugging session.

When should I not use a structured debugging playbook?▼

You should not use a structured debugging playbook when an issue is trivial or immediately obvious without instrumenting tools. It is designed for tricky issues requiring deterministic steps, evidence capture, and cross-tool observation.