deno-debugger

Debug Deno/TypeScript memory leaks, CPU bottlenecks, and race conditions via CDP profiling.

2|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/willkelly/deno-debug-skill --skill deno-debugger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deno-debugger
Source: https://github.com/willkelly/deno-debug-skill/tree/main/deno-debugger
Command: npx skills add https://github.com/willkelly/deno-debug-skill --skill deno-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Deno Debugger Skill empowers developers to reliably debug and investigate Deno/TypeScript applications by providing systematic inspection utilities, memory and CPU analysis, and automated reporting.

Core Features & Use Cases

  • Pre-written scripts for Chrome DevTools Protocol (CDP) client, heap analyzer, CPU profiler, breadcrumbs tracking, and Markdown report generation.
  • End-to-end investigation workflows for memory leaks, CPU bottlenecks, and race conditions in Deno apps.
  • Automated reporting: produces a comprehensive REPORT.md with root-cause analysis, fixes, and supporting evidence.
  • Use Case: Debug a memory leak in a Deno HTTP service by connecting to a running process, capturing heap snapshots, and generating a detailed report.

Quick Start

Install the skill by copying it into Claude's skills directory. Start your Deno app with --inspect to enable the inspector. Ask Claude to start an investigation; Claude will load prebuilt scripts and generate a report.

Frequently Asked Questions about deno-debugger

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

FAQPage Schema
How do I debug a memory leak in a Deno application?

To debug a Deno memory leak, start your app with the --inspect flag and use Chrome DevTools Protocol to capture heap snapshots. Systematic heap analysis helps identify retained objects causing the leak.

What's the best way to profile CPU bottlenecks in TypeScript?

Profiling CPU bottlenecks in TypeScript involves using CPU profilers connected via the Chrome DevTools Protocol to record execution samples. Analyzing these samples isolates expensive functions slowing your application.

How do I investigate race conditions in Deno?

Investigating race conditions in Deno requires running the application with the inspector enabled to systematically track execution breadcrumbs. Breakpoint debugging helps identify timing conflicts between concurrent operations.

Can I generate automated debugging reports for Deno performance issues?

Yes, you can generate automated debugging reports for Deno performance issues. The investigation process produces a comprehensive Markdown report containing root-cause analysis, applied fixes, and supporting profiling evidence.

Do I need to enable the inspector to use Chrome DevTools Protocol with Deno?

Yes, you must start your Deno application with the --inspect flag to enable the inspector. This exposes the Chrome DevTools Protocol endpoint required for connecting external debugging and profiling clients.