Dev Loop Debugging Strategy
Use when the user reports a bug, error message, stack trace, crash, memory leak, flaky failure or asks to find the cause or do root cause analysis. Produces a hypothesis-driven debugging plan: reproduce, isolate, bisect, instrument, fix and regression test. Not for speeding up slow code (use dev-loop-performance-profiler).
Install
npx skills add j4flmao/agent-skills --skill dev-loop-debugging-strategygit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/dev-loop/debugging-strategy ~/.claude/skills/dev-loop-debugging-strategyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Debugging Strategy
## Purpose
Apply systematic debugging methodologies — root cause analysis, scientific method for debugging, log analysis, and tool-assisted tracing — to identify, isolate, and resolve software defects efficiently.
## Agent Protocol
### Trigger
Exact user phrases: "debugging", "debug strategy", "how to debug", "root cause", "bug reproduction", "debugging methodology", "log analysis", "troubleshooting", "debug this", "why is this broken".
### Input Context
- Environment (local dev, CI, staging, production)
- Bug characteristics (reproducible, intermittent, regression, performance, crash)
- Available tools (debugger, profiler, logs, APM, metrics)
- Language and framework (affects available debugging tools)
- Recent changes (deployments, dependency updates, config changes)
- Error symptoms (error message, stack trace, incorrect output, crash dump)
### Output Artifact
Debugging plan with hypothesis, isolation strategy, reproduction steps, and root cause analysis.
### Response Format
```
Symptom: {observed vs expected}
Reproduction: {steps | not yet reproducible}
Hypotheses (ranked): {H1 -> test}, {H2 -> test}
Isolation: {bisect/binary search/minimal repro}
Root cause: {cause + evidence}
Fix + regression test: {change, test name}
```
### Completion Criteria
- [ ] Bug reproduction steps documented and confirmed
- [ ] Initial hypothesis formed with expected vs actual behavior
- [ ] Debugging tooling selected and configuredDetails
- Skill name
dev-loop-debugging-strategy- Repository
- j4flmao/agent-skills
- Path
skills/dev-loop/debugging-strategy/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Dev Loop Debugging Strategy skill do?
Use when the user reports a bug, error message, stack trace, crash, memory leak, flaky failure or asks to find the cause or do root cause analysis. Produces a hypothesis-driven debugging plan: reproduce, isolate, bisect, instrument, fix and regression test. Not for speeding up slow code (use dev-loop-performance-profiler).
How do I install the Dev Loop Debugging Strategy skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill dev-loop-debugging-strategy. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Dev Loop Debugging Strategy popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Dev Loop Refactor Guide
45j4flmao/agent-skills
Use when the user asks to refactor a long function or class safely, remove code smells, extract methods, untangle legacy code, or improve structure without changing behavior. Produces a step-by-step refactoring plan with characterization tests. Not for tracking debt backlogs (use dev-loop-tech-debt-tracker) or system migrations (use enterprise-legacy-migration).
Dev Loop API Client Generator
45j4flmao/agent-skills
Use when the user asks to generate an API client or SDK from OpenAPI/Swagger, run openapi-generator or orval, create typed REST clients, or turn requests into curl commands. Produces generated clients with auth, retries and tests. Not for designing the API itself (use backend-api-design) or writing the OpenAPI spec (use backend-openapi-documentation).
Dev Loop Tech Debt Tracker
45j4flmao/agent-skills
Use when the user asks to track technical debt, build a tech debt register, prioritize debt by interest and cost, measure code health, or set a debt budget per sprint. Produces a debt inventory with scoring and a paydown plan. Not for doing the refactor (use dev-loop-refactor-guide) or quality gates (use qc).
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.