skills.rest
nvimcraft
nvimcraftCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debugging

Diagnoses and resolves JavaScript, TypeScript, and React bugs via systematic workflow.

Updated Feb 7, 2026
Search Tags:#typescript#debugging#root cause#react#javascript#error analysis#code verification
One-click install
npx skills add https://github.com/nvimcraft/dotfiles-macos --skill debugging-nvimcraft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/nvimcraft/dotfiles-macos/tree/main/.config/opencode/skills/debugging
Command: npx skills add https://github.com/nvimcraft/dotfiles-macos --skill debugging-nvimcraft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers identify root causes of JavaScript, TypeScript, and React bugs through a disciplined debugging workflow instead of guesswork.

Core Features & Use Cases

  • Structured Debugging Workflow: Guides agents through detection, evidence gathering, reproduction, isolation, analysis, fixing, and verification.
  • Language-Specific Diagnostics: Provides targeted approaches for JavaScript runtime errors, TypeScript type failures, and React rendering or hook issues.
  • Use Case: When a React application throws a TypeError or a TypeScript build fails, use this Skill to investigate evidence, form hypotheses, apply minimal fixes, and verify the result.

Quick Start

Use the debugging skill to investigate and resolve the TypeScript error in my project following the required evidence-based workflow.

Frequently Asked Questions about debugging

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

FAQPage Schema
How do I find the root cause of a React rendering or hook error?▼

To find the root cause of a React rendering or hook error, follow a structured debugging workflow that gathers evidence, reproduces the failure, isolates the issue, applies a minimal fix, and verifies the change.

What is the best way to debug TypeScript type errors during a build?▼

The best way to debug TypeScript type errors is to use an evidence-based approach that collects failure context, forms hypotheses about type mismatches, applies minimal corrections, and verifies the result with appropriate build commands.

How do I systematically diagnose runtime errors in JavaScript applications?▼

Systematically diagnose JavaScript runtime errors by detecting the failure, gathering evidence, reproducing the issue, analyzing the execution context, applying a minimal fix, and verifying the outcome.

Can I use this systematic debugging workflow for both React and TypeScript projects?▼

Yes, you can use this systematic debugging workflow for both React and TypeScript projects, as it provides targeted diagnostic approaches for JavaScript runtime errors, TypeScript type failures, and React hook issues.

Does this debugging approach require guessing to fix code issues?▼

No, this debugging approach replaces guesswork with a disciplined workflow that requires gathering evidence, reproducing failures, analyzing hypotheses, and verifying changes to accurately resolve software issues.

Related Skills

Explore More Software Engineering Skills→
haolangehaolange
15

capture-repro

Creates deterministic capture baselines and environment snapshots for runtime debugging.

Community
Advanced
robkamrobkam
12

bugfix-red-green-proof

Enforce a red-green-proof loop starting with a failing regression test.

Community
Advanced
tobihagemanntobihagemann
399

investigate

Investigate software defects through characterize, isolate, hypothesize, and test steps.

Community
Advanced
shysssthanhtrishysssthanhtri

gitnexus-debugging

Trace runtime execution paths and error origins in GitNexus indexes.

Community
Intermediate