Index of every page on this site: llms.txt
All skills
davila7 avatar

/debugging-strategies

@053feb2
Run it yourself

Transform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches.

Use this Skill: https://skilld.dev/gh/davila7/claude-code-templates/debugging-strategies

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈42 tokens for metadata: the name and description. ≈245 when used: this file. ≈3k more on demand in 1 file.

Description uses 2.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈168 characters, or 2.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.md for detailed debugging patterns and checklists.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts24d3 checks · Risk SAFE
  • Gen Agent Trust Hub24d

    The skill provides systematic strategies and code samples for debugging software across multiple languages. It includes references to standard tools and methodologies. A low-severity risk of indirect prompt injection exists because the skill is designed to analyze potentially untrusted log files and system traces which could contain malicious instructions.

  • Socket24d

    No alerts

  • Snyk24d

    Risk: LOW · No issues

Signed by skilld at 053feb2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last month
metadata
{
  "risk": "safe",
  "source": "community",
  "date_added": "2026-02-27"
}

README badge

README badge for davila7/claude-code-templates/debugging-strategies