Debugging Troubleshooting 2025

This is a solid reference for when bash scripts misbehave in ways that make you want to throw your laptop. It covers strict mode flags (set -euo pipefail), custom PS4 prompts that show file and line numbers in traces, trap-based error handlers with stack traces, and profiling techniques for timing slow commands. The examples are copy-paste ready, like rollback-on-failure patterns and debugging why scripts work locally but break in cron. Honestly, the most useful part is the troubleshooting section on platform differences and whitespace issues, since those are the things that eat hours of your day. Good to have bookmarked when set -x alone isn't cutting it.

skills.sh installs: 196
GitHub stars: 61
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add josiahsiegel/claude-plugin-marketplace --skill debugging-troubleshooting-2025 --agent claude-code

Installs into .claude/skills of the current project.

Files

🚨 CRITICAL GUIDELINES

Windows File Path Requirements

MANDATORY: Always Use Backslashes on Windows for File Paths

When using Edit or Write tools on Windows, you MUST use backslashes (\) in file paths, NOT forward slashes (/).

Examples:

❌ WRONG: D:/repos/project/file.tsx
✅ CORRECT: D:\repos\project\file.tsx

This applies to:

Edit tool file_path parameter
Write tool file_path parameter
All file operations on Windows systems

Documentation Guidelines

NEVER create new documentation files unless explicitly requested by the user.

Priority: Update existing README.md files rather than creating new documentation
Repository cleanliness: Keep repository root clean - only README.md unless user requests otherwise
Style: Documentation should be concise, direct, and professional - avoid AI-generated tone
User preference: Only create additional .md files when user specifically asks for documentation