debug

Diagnose and resolve debugging issues using phase-based investigative workflows.

Updated Jun 23, 2025
One-click install
npx skills add https://github.com/Dayopt/app --skill debug-dayopt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/Dayopt/app/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/Dayopt/app --skill debug-dayopt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

エラー発生時や予期しない動作の報告時に、デバッグ作業を自動的に開始し、原因特定と修正を体系的に支援します。

Core Features & Use Cases

  • 自動デバッグワークフローの起動: エラーメッセージ、スタックトレース、再現手順を収集して原因追跡を支援
  • 段階的調査プロセス: Phase 1 問題理解、Phase 2 原因調査、Phase 3 仮説検証、Phase 4 修正と検証を順次実行
  • 実践的デバッグコマンドの統合: grep、git log、git diff、npm run typecheck などのユースケースを提示
  • Dayopt固有のデバッグパターン参照: tRPC、Zustand、hydration関連の問題例を含む

Quick Start

エラーまたは予期しない動作が発生した際に、このスキルを有効化して、デバッグの自動ワークフローを起動してください

Frequently Asked Questions about debug

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

FAQPage Schema
How do I automate root-cause analysis for unexpected behavior in complex codebases?

Automated root-cause analysis triggers structured investigative workflows upon error events or unexpected behavior reports. It collects stack traces and reproduction steps, guiding step-by-step diagnosis through phases like problem understanding, cause investigation, hypothesis verification, and fix validation.

What is the step-by-step debugging process for resolving errors in complex codebases?

The step-by-step debugging process follows four phases: problem understanding, cause investigation, hypothesis verification, and fix validation. It sequentially executes structured investigative workflows using commands like grep, git log, git diff, and npm run typecheck to verify changes.

Can I use automated debugging workflows for tRPC, Zustand, and hydration issues?

Automated debugging workflows support tRPC, Zustand, and hydration issues by referencing specific debugging patterns. These frameworks are covered in the cause investigation and hypothesis verification phases to systematically trace and resolve their associated unexpected behaviors.

What's the best way to troubleshoot code errors using git log and grep?

Troubleshooting code errors using git log and grep is integrated into the cause investigation phase. The workflow automatically applies these commands to trace recent changes, search relevant code sections, and systematically narrow down the root cause before proceeding to fix validation.

Why do I need a structured workflow for debugging instead of manual troubleshooting?

A structured workflow for debugging enforces end-to-end requirements, preventing skipped steps during manual troubleshooting. It automatically sequences phase-based workflows for problem understanding, investigation, and verification, ensuring fixes are validated with typecheck commands before completion.