QA Debugging
Systematic debugging methodologies, troubleshooting workflows, logging strategies, error tracking, performance profiling, stack trace analysis, and debugging tools across languages and environments. Covers local debugging, distributed systems, production issues, and root cause analysis.
Install
/plugin marketplace add Freddy-CHEN-ux/00_claude_skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Freddy-CHEN-ux/00_claude_skills --skill qa-debugginggit clone --depth 1 https://github.com/Freddy-CHEN-ux/00_claude_skills.git /tmp/00_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/00_claude_skills/skills/qa-debugging ~/.claude/skills/qa-debuggingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Debugging & Troubleshooting (Dec 2025) — Quick Reference This skill provides execution-ready debugging strategies, troubleshooting workflows, and root cause analysis techniques. Core references: Google SRE troubleshooting patterns ([Effective Troubleshooting](https://sre.google/sre-book/effective-troubleshooting/)) and SLO-driven reliability/triage ([Service Level Objectives](https://sre.google/sre-book/service-level-objectives/)); observability standards via OpenTelemetry ([Docs](https://opentelemetry.io/docs/)) and W3C Trace Context ([Spec](https://www.w3.org/TR/trace-context/)). --- ## Core QA (Default) ### Workflow (Reproduce → Isolate → Instrument → Fix → Verify → Regress) Reproduce: - Capture exact failure signature: error message, stack trace, request ID/trace ID, timestamp, build SHA, environment, user/tenant, seed/test data IDs. - Quantify reproducibility: “fails 3/20 runs” is different from “fails 20/20”. Isolate: - Reduce scope: minimal input, minimal config, smallest component boundary. - Bisect changes (git bisect / feature flags) when it started “recently”. Instrument: - Prefer structured logs + correlation IDs and traces over ad-hoc print statements ([OpenTelemetry](https://opentelemetry.io/docs/), [W3C Trace Context](https://www.w3.org/TR/trace-context/)). - Add assertions/guards to fail fast at the true boundary. Fix: - Fix root cause, not symptoms; avoid “papering over” with retries/sleeps. Verify:
Details
- Skill name
qa-debugging- Repository
- Freddy-CHEN-ux/00_claude_skills
- Path
skills/qa-debugging/SKILL.md- Repo updated
- 10 January 2026
FAQ
What does the QA Debugging skill do?
Systematic debugging methodologies, troubleshooting workflows, logging strategies, error tracking, performance profiling, stack trace analysis, and debugging tools across languages and environments. Covers local debugging, distributed systems, production issues, and root cause analysis.
How do I install the QA Debugging skill?
Claude Code plugin: /plugin marketplace add Freddy-CHEN-ux/00_claude_skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is QA Debugging popular?
It lives in Freddy-CHEN-ux/00_claude_skills, which has 8 GitHub stars and 3 forks.
Related skills
Add Integration
8Freddy-CHEN-ux/00_claude_skills
Build a new API integration for Nexus. Load when user mentions "add integration", "new integration", "integrate with", "connect to [service]", or "build [service] integration". Interactive workflow that discovers API endpoints, plans the integration, and creates a project for implementation.
AI Agents
8Freddy-CHEN-ux/00_claude_skills
Production-grade AI agent patterns with MCP integration, agentic RAG, handoff orchestration, multi-layer guardrails, and observability (modern best practices)
AI LLM
8Freddy-CHEN-ux/00_claude_skills
Production LLM engineering skill. Covers strategy selection (prompting vs RAG vs fine-tuning), dataset design, PEFT/LoRA, evaluation workflows, deployment handoff to inference serving, and lifecycle operations with cost/safety controls.
Refactoring
5vnovakovits/claude-skills
Apply Martin Fowler's refactoring discipline — changing the internal structure of code without changing its observable behavior — using the named refactorings catalog (Extract Function, Move Method, Replace Conditional with Polymorphism, etc.) and the code-smells catalog (Long Method, Feature Envy, Primitive Obsession, etc.). Use when cleaning code under a test safety net, responding to a code smell, preparing code for a new feature, or as the third step of every TDD cycle.
Product Development Flow
5vnovakovits/claude-skills
Apply Don Reinertsen's "The Principles of Product Development Flow" (Celeritas, 2009), the quantitative case for flow in product work. Covers its 175 principles across eight areas (economics, queues, variability, batch size, WIP constraints, flow control under uncertainty, fast feedback, decentralised control) with verified codes; cost of delay and the SJF, HDCF and WSJF (CD3) sequencing rules; utilisation, Little's formula and why you control queue size rather than cycle time; the batch-size U-curve; congestion collapse; cadence; pooled versus dedicated capacity; and how to handle interrupt,
Refactoring to Patterns
5vnovakovits/claude-skills
Apply Joshua Kerievsky's "Refactoring to Patterns" — the discipline of arriving at Gang of Four design patterns through refactoring driven by smells, not by upfront design. Includes the "refactor to / toward / away from a pattern" framing, the economic argument against pattern over-use, and the specific refactorings whose targets are named patterns (Factory, Strategy, Observer, Composite, Adapter, Template Method, State, Null Object). Use when a smell genuinely warrants a pattern, when undoing speculative pattern over-engineering, or when teaching the right time to introduce patterns.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.