kb-debug

Diagnose intermittent Next.js 16+ App Router and Drizzle bugs via reproduction and root-cause analysis.

Updated May 19, 2026
One-click install
npx skills add https://github.com/TimeKast/AgendaInteligente --skill kb-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kb-debug
Source: https://github.com/TimeKast/AgendaInteligente/tree/main/.claude/skills/kb-debug
Command: npx skills add https://github.com/TimeKast/AgendaInteligente --skill kb-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

kb-debug helps you resolve intermittent Next.js/React/Drizzle issues by enforcing reproduction-first investigation, root-cause analysis, and regression tests before merging fixes.

Core Features & Use Cases

  • Reproduce, then isolate: Capture exact repro steps and narrow the failure using minimal repros, component removal, or git bisect.
  • 5 Whys root-cause analysis: Convert symptoms into structural explanations tied to specific stack traces and data flow.
  • Regression-test-before-fix: Require a must-fail test against broken code, then verify it passes and run pnpm verify to protect the test pyramid.

Quick Start

Use kb-debug to diagnose a flaky hydration mismatch by documenting the repro rate, running bisect to identify the breaking commit, and writing a regression test that fails on the current bug before applying the smallest fix.

Frequently Asked Questions about kb-debug

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

FAQPage Schema
How do I debug intermittent hydration mismatches in Next.js App Router?▼

Debug Next.js hydration mismatches by enforcing a reproduce-first workflow: capture exact repro steps, isolate the failure via git bisect, and write a must-fail regression test before applying the fix.

What's the best way to find the root cause of silent Drizzle ORM failures?▼

Find root causes of silent Drizzle ORM failures by applying 5 Whys analysis to convert symptoms into structural explanations tied to specific stack traces and data flow, then verifying with regression tests.

How do I fix flaky Vitest or Playwright tests in my React application?▼

Fix flaky tests by mapping regression testing to the appropriate test layer, writing a must-fail test against broken code, and running verification commands to protect the test pyramid before merging.

Can I use this debugging workflow for race conditions in Next.js Server Actions?▼

Yes, the four-phase workflow (REPRODUCE, ISOLATE, UNDERSTAND, FIX+VERIFY) applies to race conditions in Next.js Server Actions by requiring minimal repros and root-cause verification before any fix is applied.

Why does my Next.js app work locally but fails in production with runtime errors?▼

Works-locally discrepancies are resolved by documenting reproduction rates, isolating the breaking commit with git bisect, and converting symptoms into structural explanations through 5 Whys root-cause analysis.

Does this debugging approach require writing regression tests before applying fixes?▼

Yes, it enforces regression-test-before-fix by requiring a must-fail test against broken code, then verifying the fix passes and running full verification to prevent repeat issues.