investigate

Diagnose software bug root causes through structured investigation phases.

1|2|Updated Jan 4, 2024

Search Tags:#troubleshooting #debug #investigate #code-review #root-cause #log-analysis

Ready to run

npx skills add https://github.com/NaKMiers/Port4lio --skill investigate-nakmiers

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/NaKMiers/Port4lio/tree/main/.agents/skills/investigate
Command: npx skills add https://github.com/NaKMiers/Port4lio --skill investigate-nakmiers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging with root cause investigation to prevent patching symptoms and to drive reliable fixes.

Core Features & Use Cases

Phase-driven workflow: investigate, analyze, hypothesize, implement, verify
Structured data collection: gather logs, stack traces, reproduction steps to reproduce and validate findings
Guardrails: require root-cause validation before changes and surface actionable insights for maintainers

Quick Start

Provide a structured root-cause investigation plan for the reported error.

Frequently Asked Questions about investigate

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

FAQPage Schema

How do I find the root cause of a software bug instead of just patching symptoms?▼

To find the root cause of a software bug, you need a structured investigation process that validates hypotheses against collected logs and stack traces before applying fixes. This prevents patching symptoms by enforcing root-cause validation.

What is the best way to debug complex systems with noisy log traces?▼

Debugging complex systems with noisy log traces requires a phase-driven workflow of symptom collection, code reading, and pattern analysis. This structured approach filters noise to surface actionable root causes across complex environments.

How do I perform a systematic code review for troubleshooting software errors?▼

Systematic code review for troubleshooting software errors involves a formal investigation phase to gather reproduction steps, analyze patterns, and test hypotheses. This structured data collection validates findings before implementing safe fixes.

Can I use a structured debugging workflow for diagnosing intermittent system bugs?▼

Yes, a structured debugging workflow is effective for diagnosing intermittent system bugs because it requires formal root-cause investigation, hypothesis testing, and symptom collection to reliably reproduce and validate findings before changes.

When should I use a formal root-cause investigation process for debugging?▼

You should use a formal root-cause investigation process for debugging when working across complex systems with noisy traces, as it provides guardrails to avoid patching symptoms and ensures maintainers receive actionable root cause insights.

How do I implement safe fixes after identifying a software bug's root cause?▼

To implement safe fixes after identifying a software bug's root cause, follow a phase-driven workflow that moves from hypothesis testing to implementation and verification, ensuring changes address the validated root cause directly.