gsd:workflow:diagnose-issues

Diagnose project issues by analyzing symptoms, logs, and configurations.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tDalile/dotfiles --skill gsd-workflow-diagnose-issues-tdalile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd:workflow:diagnose-issues
Source: https://github.com/tDalile/dotfiles/tree/main/agents/skills/gsd/workflows/diagnose-issues
Command: npx skills add https://github.com/tDalile/dotfiles --skill gsd-workflow-diagnose-issues-tdalile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured workflow to identify, investigate, and resolve project issues by guiding a user through symptom description, root-cause analysis, remediation planning, and implementation steps to reduce time-to-resolution.

Core Features & Use Cases

  • Symptom Documentation: Capture and articulate observable failures and reproducible steps.
  • Root Cause Investigation: Guide targeted analysis using logs, configuration inspection, and search tools to isolate causes.
  • Remediation Planning & Implementation: Prioritize fixes, outline remediation steps, and track implementation progress.
  • Use Case: Triage a failing CI job by describing symptoms, searching build logs for errors, hypothesizing causes, and producing a prioritized fix plan.

Quick Start

Diagnose the reported failures by listing symptoms, collecting relevant logs and configuration, investigating likely root causes, and proposing a prioritized remediation plan.

Frequently Asked Questions about gsd:workflow:diagnose-issues

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

FAQPage Schema
How do I troubleshoot software failures and find their root cause?

To troubleshoot software failures and find their root cause, document observable symptoms, analyze logs, inspect code and configuration, narrow hypotheses, and outline prioritized remediation steps.

What's the best way to diagnose a failing CI job and plan a fix?

To diagnose a failing CI job, describe the symptoms, search build logs for errors, hypothesize likely causes, and produce a prioritized fix plan to guide implementation and reduce time-to-resolution.

Can I use this workflow for operational issue triage and log analysis?

Yes, you can use this workflow for operational issue triage and log analysis. It applies to both software and operational workflows to triage symptoms, inspect configurations, and plan remediation.

How do I structure a root-cause investigation for complex project issues?

Structure a root-cause investigation by moving through multiple phases: document symptoms, collect relevant logs, investigate likely causes using targeted searches, and propose a prioritized remediation plan.

Does this triage workflow require external search or grep dependencies?

No, this triage workflow requires no external dependencies. It provides a structured reasoning process to guide log analysis and code inspection rather than relying on specific external components.