skills.rest
WhatIfWeDigDeeper
WhatIfWeDigDeeperCOMMUNITY
Explore all skills by this author →
GitHub

debug

Diagnose and fix bugs in Node.js/React projects using a structured debugging workflow.

Updated Jan 13, 2026
Search Tags:#typescript#debugging#nodejs#root-cause#bug-fix#regression-test#reproduce-issue
One-click install
npx skills add https://github.com/WhatIfWeDigDeeper/claude-template --skill debug-whatifwedigdeeper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/WhatIfWeDigDeeper/claude-template/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/WhatIfWeDigDeeper/claude-template --skill debug-whatifwedigdeeper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate and fix bugs systematically by following a structured debugging workflow, from reproducing the issue to validating a fix.

Core Features & Use Cases

  • Reproduce the Issue: steps to reproduce and confirm bug exists.
  • Gather Information: check recent changes, logs, build/tests.
  • Locate the Problem: search strategies for code paths.
  • Understand Root Cause: reason about difference between expected and actual.
  • Develop Fix: apply minimal changes.
  • Add Regression Test: introduce test capturing scenario.
  • Validate: run build, lint, tests.
  • Document: summarize bug, root cause, fix, test.

Quick Start

Describe the bug with a concise description to trigger the debugging workflow and guide the agent to reproduce and fix it.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I systematically debug a Node.js or TypeScript issue?▼

Diagnose and fix bugs in Node.js or TypeScript by following a structured debugging workflow that reproduces the issue, gathers context from git history and logs, locates the root cause, and validates the fix with regression tests.

What is the best way to find a root cause when a bug is hard to reproduce?▼

Locating a root cause involves gathering context from recent git history and test runs, searching code paths, and reasoning about the difference between expected and actual software behavior to pinpoint the failure.

Can I use this debugging workflow to fix bugs in React projects?▼

Yes, the structured debugging workflow applies to development environments across Node.js and React projects, requiring access to repository history, tests, and build commands to verify fixes.

How do I add a regression test after implementing a bug fix?▼

Add a regression test by introducing a specific test that captures the bug scenario, then run build, lint, and npm test commands to validate the fix and prevent future regressions.

Why do I need access to git log and npm test commands for debugging?▼

Access to git log and npm test commands is required to gather context on recent changes, understand the root cause, and validate that the implemented bug fix passes all build and test checks.

Related Skills

Explore More Software Engineering Skills→
lpjhelderlpjhelder

forge-setup

Install and configure kronon-forge with Node.js and npm.

Community
Intermediate
withzombieswithzombies
80

fixing-bugs

Automate bug fixing from issue creation through regression testing and closure.

Community
Advanced
mattbobambrosemattbobambrose
1

add-tests

Add unit and integration tests to fill coverage gaps in source repositories.

Community
Advanced
kynoptickynoptic
1

Debugging Runtime Errors

Analyze stack traces and error logs to identify root causes and propose fixes.

Community
Advanced