skills.rest
jason660519
jason660519COMMUNITY
Explore all skills by this author →
GitHub

investigate

Debug Tauri, Next.js, and Rust projects through a five-phase root-cause workflow.

Updated May 11, 2026
Search Tags:#debug#ingestion#investigate#root-cause#stack-trace#ipc#bug-triage
One-click install
npx skills add https://github.com/jason660519/Project-Manager --skill investigate-jason660519
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/jason660519/Project-Manager/tree/main/.agents/skills/investigate
Command: npx skills add https://github.com/jason660519/Project-Manager --skill investigate-jason660519

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging with root-cause investigation for Project Manager's Tauri + Next.js + Rust stack. The Iron Law: no fix without root-cause first, and a five-phase approach (Investigate / Pattern Analysis / Hypothesis Testing / Implementation / Verification & Report) to guide operations. Use when users report bugs, stack traces, unexpected UI states, IPC failures, ingestion crashes, or requests to debug / fix / root-cause / why is this broken. Proactively invoke instead of guessing fixes.

Core Features & Use Cases

  • Five-phase debugging workflow: Investigate, Pattern Analysis, Hypothesis Testing, Implementation, Verification & Report.
  • Context gathering and deterministic reproduction steps to isolate root causes across UI, ingestion, and IPC layers.
  • Proactive debugging assistant that suggests hypotheses only after collecting symptoms and traces.

Quick Start

Describe the observed symptom and steps to reproduce, then initiate the root-cause investigation workflow.

Frequently Asked Questions about investigate

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

FAQPage Schema
How do I debug intermittent IPC failures in a Tauri and Next.js project?▼

A systematic root-cause debugging workflow prevents guessing fixes by enforcing a five-phase approach: Investigate, Pattern Analysis, Hypothesis Testing, Implementation, and Verification. It collects symptoms and traceable evidence across UI, ingestion, and IPC layers to verify root causes before applying fixes.

What is the best way to find the root cause of a stack trace in a Rust backend?▼

Finding a stack trace root cause requires applying pattern analysis and hypothesis testing against collected symptoms. The debugging workflow enforces verifying root causes with traceable evidence across the Rust stack before implementing any code fixes.

How do I systematically triage bugs across a Tauri, Next.js, and Rust stack?▼

Systematic bug triage across the Tauri, Next.js, and Rust stack requires a five-phase workflow: Investigate, Pattern Analysis, Hypothesis Testing, Implementation, and Verification & Report. It enforces gathering reproduction steps and traceable evidence before fixing.

Can I use this debugging workflow for ingestion crashes and unexpected UI states?▼

Yes, the debugging workflow applies to ingestion crashes and unexpected UI states. It proactively initiates root-cause investigation by collecting symptoms, reproduction steps, and traceable evidence across the Project Manager stack before suggesting fixes.

Why does fixing bugs without finding the root cause fail in complex stacks?▼

Fixing bugs without root-cause analysis fails because it guesses fixes without traceable evidence. The systematic debugging workflow enforces collecting symptoms and verifying hypotheses first to ensure the actual source of UI, IPC, or ingestion issues is resolved.

Related Skills

Explore More Software Engineering Skills→
louisfghbvclouisfghbvc
4

investigate

Guide a debugging workflow to identify root causes of software defects.

Community
Advanced
bizzybaebizzybae

investigate

Systematically debugs errors through four phases: investigate, analyze, hypothesize, implement.

Community
Advanced
ibnuhalimmibnuhalimm

Debug

Reproduce and solve bugs through structured phases and root-cause analysis.

Community
Advanced
yashs33244yashs33244
1

gstack-openclaw-investigate

Guide root-cause investigation and verified bug fixing for software failures.

Community
Advanced