Automated summary
This skill walks the agent through a methodical debugging process: reproducing the issue, forming hypotheses, running controlled experiments, and narrowing scope until the root cause is found.
Strengths
- Enforces a hypothesis → experiment → verify loop instead of random code changes
- Applies to application bugs, production incidents, crash dumps, and distributed systems alike
- Recommends binary search and targeted instrumentation to isolate the cause quickly
- Points to a detailed playbook (resources/implementation-playbook.md) for harder cases
Limitations
- The SKILL.md itself contains no concrete techniques; the substantive guidance lives in the resource file
- Assumes access to logs, traces, or runtime signals — without them the method stays theoretical
- Does not address non-reproducible symptoms or deep performance profiling
Use it whenever a bug or incident has an observable symptom and needs to be tracked down systematically rather than by guesswork.
Avoid it when there is no reproducible symptom or no access to logs and traces, or when the task is ordinary feature development.
Security analysis
SafeThe skill contains only instructional text about debugging strategies, with no declared tools, commands, or actions that could execute code, modify systems, or access sensitive data. There is no execution risk.
No concerns found
How this analysis is madeExamples
Our checkout API returns 500 errors for about 2% of requests in production but never locally. Help me debug this systematically — I can share logs and traces.One integration test fails roughly once every 20 CI runs with a timeout. Guide me through forming hypotheses and narrowing down the cause instead of just adding retries.Latency in our order service spikes for a few minutes every hour and we suspect a downstream dependency. Walk me through a structured investigation using our traces.name: debugging-strategies description: "Transform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches." risk: safe source: community date_added: "2026-02-27"
Debugging Strategies
Transform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches.
Use this skill when
- Tracking down elusive bugs
- Investigating performance issues
- Debugging production incidents
- Analyzing crash dumps or stack traces
- Debugging distributed systems
Do not use this skill when
- There is no reproducible issue or observable symptom
- The task is purely feature development
- You cannot access logs, traces, or runtime signals
Instructions
- Reproduce the issue and capture logs, traces, and environment details.
- Form hypotheses and design controlled experiments.
- Narrow scope with binary search and targeted instrumentation.
- Document findings and verify the fix.
- If detailed playbooks are required, open
resources/implementation-playbook.md.
Resources
resources/implementation-playbook.mdfor detailed debugging patterns and checklists.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/debugging-strategies-msh3utli/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/debugging-strategies-msh3utli' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/debugging-strategies-msh3utli/download' --output '.skill-downloads/debugging-strategies-msh3utli/SKILL.md.part' && mv '.skill-downloads/debugging-strategies-msh3utli/SKILL.md.part' '.skill-downloads/debugging-strategies-msh3utli/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/debugging-strategies-msh3utli/SKILL.md' && test -s '.skill-downloads/debugging-strategies-msh3utli/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/debugging-strategies' && cp -R '.skill-downloads/debugging-strategies-msh3utli' '.claude/skills/debugging-strategies'Cursor
test -f '.skill-downloads/debugging-strategies-msh3utli/SKILL.md' && test -s '.skill-downloads/debugging-strategies-msh3utli/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/debugging-strategies' && cp -R '.skill-downloads/debugging-strategies-msh3utli' '.cursor/skills/debugging-strategies'Codex
test -f '.skill-downloads/debugging-strategies-msh3utli/SKILL.md' && test -s '.skill-downloads/debugging-strategies-msh3utli/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/debugging-strategies' && cp -R '.skill-downloads/debugging-strategies-msh3utli' '.agents/skills/debugging-strategies'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/debugging-strategies-msh3utli'openskills read 'debugging-strategies-msh3utli'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/debugging-strategies-msh3utli/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.