systematic-debugging
About
This Claude Skill provides systematic debugging guidance to help developers find root causes before implementing fixes. It's triggered by debugging scenarios like test failures, unexpected behavior, or errors, emphasizing evidence-based investigation over quick solutions. The skill ensures developers understand exactly why something is broken before attempting repairs, preventing wasted time and new issues.
Quick Install
Claude Code
Recommendednpx skills add TechNickAI/ai-coding-config -a claude-code/plugin add https://github.com/TechNickAI/ai-coding-configgit clone https://github.com/TechNickAI/ai-coding-config.git ~/.claude/skills/systematic-debuggingCopy and paste this command in Claude Code to install this skill
GitHub Repository
Related Skills
systematic-debugging
OtherThis skill provides a structured four-phase debugging framework to replace random code changes with systematic problem diagnosis. It helps developers methodically investigate bugs, errors, and unexpected behavior by forming specific hypotheses and testing single changes. Use it when under time pressure or when quick fixes seem obvious to ensure reliable problem resolution.
verification-before-completion
OtherThis debugging skill enforces mandatory verification before claiming any task as complete. It requires developers to run full verification commands, thoroughly examine their output, and confirm results before declaring work finished. This evidence-based approach is particularly crucial before commits, pull requests, or task completion to ensure quality and accuracy.
verification-before-completion
OtherThis skill enforces running verification commands and confirming their output before claiming any task is complete. It's designed for use before commits, PRs, or task completion to ensure evidence-based claims. The skill provides structured workflows and patterns to integrate mandatory verification into your development process.
mcp-debug
OtherThe mcp-debug skill enables developers to test and debug MCP servers in real-time by directly calling MCP tools and inspecting raw responses. It's designed for diagnosing unexpected data, verifying server connectivity, and exploring MCP capabilities during development sessions. This skill uses mcptools for MCP communication and is ideal when working across application and MCP server repositories.
