debugging-tools

Name: debugging-tools
Availability: InStock
Author: Samuelca6399

Diagnose frontend, Node.js, native, and networking defects with specialized debugging tools.

Updated Aug 23, 2026

Search Tags:#debugging #network-troubleshooting #chrome-devtools #node-inspector #strace #memory-profiling #core-dumps

Ready to run

npx skills add https://github.com/Samuelca6399/AbsolutelySkilled --skill debugging-tools-samuelca6399

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging-tools
Source: https://github.com/Samuelca6399/AbsolutelySkilled/tree/main/skills/debugging-tools
Command: npx skills add https://github.com/Samuelca6399/AbsolutelySkilled --skill debugging-tools-samuelca6399

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps you diagnose and fix bugs systematically when you need to inspect frontend behavior, backend runtime state, OS-level behavior, or network interactions.

Core Features & Use Cases

Chrome DevTools workflows: Use Performance, Memory, and Sources techniques (breakpoints, logpoints) to find slow rendering, long tasks, and memory leaks.
Node.js debugging: Attach or start Node with the inspector protocol to step through code and inspect state at runtime.
System-level tracing: Use strace/ltrace to understand failing syscalls and library calls, plus lldb for core dump/crash analysis.
Network investigation: Diagnose request/connection/TLS timing with curl and capture traffic with tcpdump/Wireshark to locate where failures occur.

Quick Start

Ask for a Chrome DevTools plan to investigate a slow React page by recording a Performance trace and identifying the top contributors in the Flame Chart and Long Tasks.

Frequently Asked Questions about debugging-tools

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

FAQPage Schema

How do I debug a memory leak in a Node.js backend using the inspector protocol?▼

Debug a Node.js memory leak by attaching via the inspector protocol to step through code at runtime, inspect state, and capture heap snapshots to identify retained objects causing the leak.

What is the best way to investigate slow React rendering with Chrome DevTools?▼

The best way to investigate slow React rendering is to record a Chrome DevTools Performance trace, then analyze the Flame Chart and Long Tasks to identify the top JavaScript contributors blocking the main thread.

How does strace help with troubleshooting failing syscalls in native applications?▼

Strace helps with troubleshooting failing syscalls by tracing the library and system calls made by a process, allowing you to filter outputs and understand exactly where an OS-level failure occurs.

Can I use tcpdump and Wireshark to diagnose network connection and TLS timing issues?▼

Yes, you can use tcpdump to capture network packet traffic and Wireshark to inspect it, allowing you to diagnose request, connection, and TLS timing to locate exactly where network failures occur.

How do I analyze core dumps and native crashes using lldb backtraces?▼

Analyze core dumps and native crashes using lldb backtraces to inspect the call stack at the moment of failure, enabling you to triage the crash and pinpoint the root cause of the defect.

Do I need a structured workflow to reproduce and isolate variables when debugging?▼

Yes, a structured workflow is required to systematically reproduce the issue, isolate variables, and validate hypotheses using tool-specific techniques to pinpoint the root cause of defects accurately.