afc:debug

Diagnose software bugs and implement targeted fixes from error traces.

7|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/jhlee0409/all-for-claudecode --skill afc-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: afc:debug
Source: https://github.com/jhlee0409/all-for-claudecode/tree/main/skills/debug
Command: npx skills add https://github.com/jhlee0409/all-for-claudecode --skill afc-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you identify the root cause of bugs, errors, or unexpected behavior in your code and provides a targeted fix.

Core Features & Use Cases

  • Root Cause Analysis: Systematically investigates errors using traces, data flow, and state analysis.
  • Hypothesis Generation: Creates and evaluates potential causes for bugs, prioritizing the most likely ones.
  • Automated Fixing: Applies minimal, impactful changes to resolve confirmed bugs.
  • Use Case: When your application crashes with an unhandled exception, you can use this Skill to pinpoint the exact line of code causing the issue and automatically correct it.

Quick Start

Use the afc:debug skill to diagnose and fix the 'TypeError: cannot read property of undefined' error.

Frequently Asked Questions about afc:debug

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

FAQPage Schema
How do I identify the root cause of an unhandled exception in my codebase?

To identify the root cause of an unhandled exception, this Skill automates diagnosis by analyzing error messages, stack traces, data flow, and recent code changes to pinpoint the exact line of code causing the issue.

Can I automatically fix a TypeError where a property is read from undefined?

Yes, you can automatically fix a TypeError by using this Skill to apply minimal, impactful changes to resolve confirmed bugs. It validates fixes through a critic loop and automated verification steps.

What is the best way to debug unexpected application behavior using stack traces?

The best way to debug unexpected behavior is using root cause analysis that evaluates hypotheses based on stack traces and state analysis. It prioritizes the most likely potential causes for bugs and implements targeted fixes.

How does automated bug fixing validate code changes without breaking existing logic?

Automated bug fixing validates code changes by running a critic loop and automated verification steps after applying targeted fixes. This ensures the minimal changes made to resolve confirmed bugs do not break existing logic.

When should I use automated root cause analysis instead of manual code review?

You should use automated root cause analysis instead of manual code review when your application crashes with an unhandled exception and you need to systematically investigate error messages and recent code changes to implement targeted fixes.