skills.rest
cshyang
cshyangCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gsd:workflow:diagnose-issues

Diagnose project issues by collecting symptoms and identifying probable root causes.

Updated Mar 15, 2026
Search Tags:#workflow#debugging#remediation#diagnose#root-cause#software
One-click install
npx skills add https://github.com/cshyang/nochore --skill gsd-workflow-diagnose-issues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd:workflow:diagnose-issues
Source: https://github.com/cshyang/nochore/tree/main/capabilities/incubator/skills/gsd/workflows/diagnose-issues
Command: npx skills add https://github.com/cshyang/nochore --skill gsd-workflow-diagnose-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Workflow for diagnosing and resolving project issues.

Core Features & Use Cases

  • Symptom collection: capture visible signs of trouble and corroborate with logs.
  • Root-cause analysis: identify underlying causes across affected components.
  • Remediation planning: outline steps to fix issues and validate outcomes.

Quick Start

Describe the current project issue and ask the workflow to diagnose symptoms, identify root causes, and plan fixes.

Frequently Asked Questions about gsd:workflow:diagnose-issues

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

FAQPage Schema
What is the best way to diagnose software project issues like build failures?▼

Diagnosing software project issues requires collecting visible symptoms and corroborating them with logs to identify probable root causes. This structured workflow captures signs of trouble across affected components to plan fixes.

How do I perform root-cause analysis for flaky tests and performance regressions?▼

Root-cause analysis for flaky tests and performance regressions involves capturing symptoms and identifying underlying causes across affected components. This workflow systematically outlines remediation steps to validate outcomes.

Can I use this workflow to plan remediation for any debugging scenario?▼

Yes, you can use this workflow to plan remediation for debugging scenarios. It is applicable to software projects, satisfying requirements for structured symptom capture, root-cause analysis, and implementation tracking.

How do I start diagnosing a project issue using this workflow?▼

To start diagnosing a project issue, describe the current problem and ask the workflow to collect symptoms, identify root causes, and plan fixes. It guides you through capturing signs of trouble and corroborating with logs.

Does this workflow track implementation after planning fixes?▼

Yes, this workflow tracks implementation after planning fixes. It satisfies requirements for structured remediation planning and implementation tracking to ensure issues are fully resolved and outcomes are validated.

Why does my software need structured symptom capture for debugging?▼

Structured symptom capture is needed for debugging to systematically record visible signs of trouble and corroborate them with logs. This ensures accurate root-cause identification across components before planning fixes.

Related Skills

Explore More Software Engineering Skills→
derHakenderHaken
437

systematic-debugging

Trace data flow and apply a four-phase process to fix root causes.

Community
Advanced
baskarajatibaskarajati

fix-review

Trace git commits to security audit findings and generate remediation reports.

Community
Advanced
ianphilianphil

tmux-tdd

Monitor tmux pane test output to drive the RED-GREEN-REFACTOR workflow.

Community
Intermediate
amanikamanik

investigate

Trace error symptoms to underlying causes using a structured four-phase debugging workflow.

Community
Advanced