skills.rest
anthropics
anthropicsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

debug

Guide structured debugging to isolate root causes and propose fixes.

23.4k|2.8k|Updated Jan 23, 2026
Search Tags:#code analysis#debugging#troubleshooting#logs#bug fixing#error resolution
One-click install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill debug-anthropics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/anthropics/knowledge-work-plugins/tree/main/engineering/skills/debug
Command: npx skills add https://github.com/anthropics/knowledge-work-plugins --skill debug-anthropics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured approach to diagnosing and fixing software bugs and unexpected behavior, saving time and reducing frustration when issues arise.

Core Features & Use Cases

  • Reproduce Issues: Clearly defines expected vs. actual behavior and outlines steps to reliably trigger a bug.
  • Isolate Root Cause: Guides the user through narrowing down the problem area by checking logs, recent changes, and code paths.
  • Propose Fixes: Helps formulate and document a solution, including considerations for side effects and regression prevention.
  • Use Case: When a feature suddenly stops working after a deployment, use this Skill to systematically trace the issue from the error message back to the faulty code change.

Quick Start

Use the debug skill with the error message "TypeError: 'NoneType' object is not iterable" to start troubleshooting.

Frequently Asked Questions about debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I systematically debug a software issue after a deployment?▼

Systematic debugging involves reproducing the error, isolating the root cause by checking logs and recent changes, tracing code paths, and proposing fixes with regression prevention.

What is the best way to isolate a root cause from application logs?▼

Isolating a root cause from logs involves narrowing down the problem area by checking logs against recent source control changes and tracing code paths to pinpoint the faulty behavior.

Can I integrate source control and monitoring tools for troubleshooting?▼

Yes, troubleshooting supports integration with monitoring, source control, and project tracking tools to comprehensively trace errors back to faulty code changes.

How do I fix a TypeError like 'NoneType' object is not iterable?▼

Troubleshooting a TypeError like 'NoneType' object is not iterable starts by using the error message to reproduce the issue, trace the code path returning None, and propose a targeted fix.

Why should I document solutions and preventative measures when fixing bugs?▼

Documenting solutions and preventative measures during bug fixing helps formulate a complete resolution, consider side effects, and ensure regression prevention for comprehensive issue resolution.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
ref-docsref-docs

bug-hunter

Reproduce software bugs, analyze causes, and generate fix plans.

Official
Advanced
xtrm-devxtrm-dev
4

gitnexus-debugging

Trace execution paths and callers to identify root causes of code failures.

Official
Intermediate
ArabelaTsoArabelaTso
142

static-bug-detector

Analyze source code statically to detect functional bugs and report locations with severity.

Community
Advanced