Verified:GitHub

debugging-tools

Name: debugging-tools
Availability: InStock
Author: AbsolutelySkilled

Diagnoses multi-software bugs across browsers, servers, and native apps using Chrome DevTools, strace, lldb, curl, and memory profiling.

207|31|Updated Mar 14, 2026

Search Tags:#debugging #memory #profiling #devtools #lldb #strace

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematic debugging across browser front-ends, Node.js servers, and native processes can be tedious and error-prone. This skill provides a structured workflow and tool guidance to reproduce bugs, isolate root causes, and apply fixes quickly.

Core Features & Use Cases

Chrome DevTools workflow for performance, memory, and network debugging.
Strace, ltrace, and gdb/lldb workflows for native process debugging.
Memory profiling, heap snapshots, and diagnostic reports to identify leaks and regressions.
Cross-platform guidance covering web apps, APIs, and native binaries.

Quick Start

Activate debugging-tools and run a guided debugging session to reproduce and diagnose a sample issue.

Frequently Asked Questions about debugging-tools

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

FAQPage Schema

How do I debug memory leaks and performance issues across web and native applications?▼

Memory debugging across web and native apps requires structured workflows like Chrome DevTools heap snapshots for browsers and lldb for native binaries. This skill guides agents through reproducibility, isolation, and root-cause analysis to identify leaks and regressions reliably.

What is the best way to systematically isolate a bug in a Node.js backend service?▼

Systematic bug isolation in a Node.js backend involves structured problem framing and reproducible repro steps. This skill provides guided workflows using curl and diagnostic reports to trace server behavior, moving from reproduction to root-cause analysis.

Can I use strace and lldb to diagnose multi-layer software bugs in native processes?▼

Yes, diagnosing native process bugs with strace and lldb is fully supported. The skill provides workflows for tracing system calls and library calls, enabling AI agents to isolate root causes across native binaries and backend services.

How do I reproduce a frontend browser bug before isolating the root cause?▼

Reproducing a frontend browser bug requires structured problem framing and reproducible steps using Chrome DevTools. This skill guides agents through performance, memory, and network debugging workflows to systematically isolate the root cause.

When should I use memory profiling and heap snapshots for debugging?▼

Memory profiling and heap snapshots should be used when diagnosing memory leaks and performance regressions in web applications. The skill provides structured diagnostic workflows to capture and analyze these reports for reliable root-cause identification.