troubleshooting

Generate codebase-aware troubleshooting documentation with diagnostic procedures and recovery steps.

5|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/SteveFeldman/agents-skills --skill troubleshooting-stevefeldman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshooting
Source: https://github.com/SteveFeldman/agents-skills/tree/main/skills/troubleshooting
Command: npx skills add https://github.com/SteveFeldman/agents-skills --skill troubleshooting-stevefeldman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of comprehensive, codebase-aware troubleshooting documentation, reducing the time and effort required to diagnose and resolve system issues.

Core Features & Use Cases

  • Codebase Analysis: Understand application structure, dependencies, and critical paths.
  • Failure Mode Identification: Pinpoint potential points of failure within the application.
  • Diagnostic Procedure Generation: Create step-by-step guides for identifying root causes.
  • Error Code Documentation: Catalog and explain specific error messages and codes.
  • Recovery and Escalation: Define clear steps for issue resolution and escalation.
  • Use Case: When a critical service experiences intermittent failures, this Skill can generate a detailed troubleshooting guide that includes specific log locations, diagnostic commands, and potential recovery steps tailored to the application's architecture.

Quick Start

Use the troubleshooting skill to generate a diagnostic procedure for the authentication service.

Frequently Asked Questions about troubleshooting

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

FAQPage Schema
How do I generate troubleshooting documentation for my application's failure modes?

To generate troubleshooting documentation, the Skill analyzes your codebase structure and dependencies to pinpoint potential failure modes, producing step-by-step diagnostic procedures and error references tailored to your application architecture.

What is the best way to create an incident response runbook for system maintenance?

Creating an incident response runbook is best handled by analyzing your application's critical paths to document environment-specific issues, define severity levels, and outline clear recovery and escalation steps for system maintenance.

How do I document error codes and diagnostic procedures for an intermittent service failure?

Documenting error codes for intermittent service failures involves cataloging specific error messages from your application logs and generating diagnostic procedures that identify specific log locations and potential recovery steps.

Can I use this to generate environment-specific recovery steps for my software engineering team?

Yes, you can generate environment-specific recovery steps by having the Skill analyze your application structure to define severity levels and document actionable guides tailored to your software engineering team's incident response needs.

What limitations exist when generating codebase-aware troubleshooting guides for complex dependencies?

Limitations when generating codebase-aware troubleshooting guides depend on the accuracy of the application structure analysis; if dependencies and critical paths are not properly identified, the generated diagnostic procedures and recovery steps may lack necessary context.