skills.rest
latitude-dev
latitude-devOFFICIAL
Explore all skills by this author →
Website𝕏@trylatitudeGitHub

analyze-problem

Analyze bug reports to identify root causes and propose fixes.

4.6k|378|Updated Jun 28, 2024
Search Tags:#debugging#troubleshooting#remediation#analyze#root-cause#bug-report
One-click install
npx skills add https://github.com/latitude-dev/latitude-llm --skill analyze-problem
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze-problem
Source: https://github.com/latitude-dev/latitude-llm/tree/main/.agents/skills/analyze-problem
Command: npx skills add https://github.com/latitude-dev/latitude-llm --skill analyze-problem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams understand issues by providing a structured analysis that identifies observable symptoms, potential root causes, recommended remediation, and a plan for validation.

Core Features & Use Cases

  • In-depth issue analysis: produce a clear, evidence-based explanation of the problem as observed.
  • Root-cause identification: trace data flow and state to pinpoint the underlying cause.
  • Fix proposal & verification: outline concrete changes and a minimal verification plan to prevent regressions.
  • Use Case: When a bug report is ambiguous, generate a precise diagnostic report with actionable next steps.

Quick Start

Analyze the bug report or task, identify root causes, propose fixes, verify results.

Frequently Asked Questions about analyze-problem

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

FAQPage Schema
How do I find the root cause of a bug from an ambiguous report?▼

To find the root cause of a bug, analyze the report to trace data flow, state, and side effects through the codebase. This maps observable symptoms to entry points and pinpoints underlying causes using evidence-based diagnostics.

What is the best way to structure bug remediation and prevent regressions?▼

The best way to structure bug remediation is to outline concrete code changes alongside a minimal verification plan. This specifies exact checks to validate the fix and prevent regressions before deployment.

How do I analyze codebase data flow to troubleshoot an issue?▼

To analyze codebase data flow for troubleshooting, map the issue to involved entry points and trace state changes. This maps observable symptoms through the codebase to identify suspected root causes.

Can I generate a diagnostic report from an ambiguous bug report?▼

Yes, you can generate a precise diagnostic report from an ambiguous bug report. The analysis produces a structured explanation of observable symptoms, suspected root causes, and actionable next steps for remediation.

Why does tracing state and side effects help with debugging?▼

Tracing state and side effects helps with debugging by mapping how data transforms across entry points. This evidence-based approach traces symptoms through the codebase to pinpoint the underlying cause accurately.

Related Skills

Explore More Software Engineering Skills→
tonehqtonehq
11

foundational

Document foundational pipecat code, examples, and internal APIs for developers.

Official
Intermediate
tomguntomgun

fixing-bugs

Reproduce bugs with regression tests and apply minimal root-cause fixes.

Community
Intermediate
PiLastDigitPiLastDigit
597

TRIP-4-test

Automate unit, integration, and regression tests on changed files.

Community
Advanced
Mekann2904Mekann2904

log-analyzer

Analyze log files to extract error patterns and detect anomalies.

Community
Intermediate