skills.rest
truongnat
truongnatCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

investigate

Analyze codebase issues and bugs to identify root causes and propose solutions.

1|Updated Jul 3, 2026
Search Tags:#code review#investigation#root cause analysis#bug investigation#technical analysis
One-click install
npx skills add https://github.com/truongnat/simple-skills --skill investigate-truongnat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/truongnat/simple-skills/tree/main/skills/investigate
Command: npx skills add https://github.com/truongnat/simple-skills --skill investigate-truongnat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured approach to investigate codebase issues, bugs, and technical questions before implementing solutions, ensuring a thorough understanding of the problem.

Core Features & Use Cases

  • Problem Description: Captures detailed problem descriptions and expected/actual behaviors.
  • Evidence Collection: Facilitates the collection of evidence such as logs, errors, and reproduction steps.
  • Root Cause Analysis: Guides through the process of identifying root causes and making evidence-based recommendations.
  • Use Case: Before implementing a fix for a production issue, use this Skill to analyze logs, code, and system behavior to confirm the root cause and propose a solution.

Quick Start

Start a new investigation by creating an 'INVESTIGATE.md' file in the current directory.

Frequently Asked Questions about investigate

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

FAQPage Schema
How do I perform a root cause analysis for a bug before implementing a fix?▼

Root cause analysis for a bug involves collecting evidence like logs and reproduction steps, analyzing the codebase to identify the underlying issue, and proposing an evidence-based solution before implementation begins.

What is the best way to document a codebase investigation and track technical evidence?▼

Documenting a codebase investigation is best done using structured markdown notes to capture problem descriptions, track collected evidence like errors and logs, and record identified root causes and recommendations.

How do I start a technical analysis of a production issue in my current directory?▼

Start a technical analysis of a production issue by creating an INVESTIGATE.md file in your current directory to structure your problem description, expected versus actual behaviors, and collected evidence.

When do I need a structured investigation process for technical questions?▼

A structured investigation process is needed when you must confirm the root cause of a technical question or bug before writing code, ensuring a thorough understanding of the problem and preventing incorrect fixes.

Does this approach to bug investigation require any external dependencies or tools?▼

This approach to bug investigation requires no external dependencies, relying solely on markdown for structured investigation notes and evidence tracking to analyze codebase issues and propose solutions.

Related Skills

Explore More Software Engineering Skills→
pcasarettopcasaretto

bug-reproduction-validator

Reproduce reported software issues and classify them as bugs, environmental problems, or user errors.

Community
Advanced
hungtrandigitalhungtrandigital

debugging

Guide root-cause investigation through a four-phase systematic debugging workflow.

Community
Advanced
Covcloud-LLCCovcloud-LLC

diagnose

Reproduce failure paths and trace execution to identify root causes.

Official
Advanced
aniruddh2003aniruddh2003
1

speckit.checker

Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.

Community
Intermediate