afc:analyze

Analyze code and trace execution flows in read-only mode.

7|Updated Feb 19, 2026

Search Tags:#code analysis #debugging #system understanding #codebase exploration #flow tracing #component inspection

Ready to run

npx skills add https://github.com/jhlee0409/all-for-claudecode --skill afc-analyze

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: afc:analyze
Source: https://github.com/jhlee0409/all-for-claudecode/tree/main/skills/analyze
Command: npx skills add https://github.com/jhlee0409/all-for-claudecode --skill afc-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers quickly understand complex codebases by analyzing code, tracing execution flows, auditing consistency, and inspecting components without making any changes.

Core Features & Use Cases

Code Analysis: Deep dives into specific code sections or entire components.
Flow Tracing: Maps out how data and execution move through the system.
Auditing: Checks for consistency and adherence to project standards.
Component Inspection: Provides detailed information about how parts of the system work.
Use Case: A developer needs to understand a bug in a new feature. They can use /afc:analyze to trace the user authentication flow, identify potential race conditions, and pinpoint the exact lines of code causing the issue.

Quick Start

Use the afc:analyze skill to trace the user login flow in the codebase.

Frequently Asked Questions about afc:analyze

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

FAQPage Schema

How do I trace execution flows in a complex codebase without modifying files?▼

Read-only code analysis traces execution flows in a complex codebase without modifying files by mapping data movement and pinpointing root causes. It inspects system components and audits consistency safely using project configuration files for context.

What is the best way to perform root cause analysis on unfamiliar code?▼

The best way to perform root cause analysis on unfamiliar code is through exploratory code analysis that traces execution paths and inspects components. This identifies exact lines causing issues by leveraging project configuration files for contextual understanding.

Can I audit codebase consistency using project configuration files?▼

Yes, you can audit codebase consistency using project configuration files like CLAUDE.md. The analysis process checks adherence to project standards and inspects system components in read-only mode to ensure structural consistency without modifying any files.

Does codebase exploration support comparative analysis of different system components?▼

Yes, codebase exploration supports comparative analysis of different system components alongside root cause and structural analysis modes. It provides insights by inspecting how parts of the system work relative to each other without altering the underlying files.

When should I not use read-only code analysis for debugging?▼

You should not use read-only code analysis for debugging when you need to actively modify code to test fixes or patch vulnerabilities. This approach strictly provides insights and traces flows without writing changes to the actual files.