explain

Explain code, features, and architecture by reading code and tracing calls.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/drimchansky/agents-kit --skill explain-drimchansky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explain
Source: https://github.com/drimchansky/agents-kit/tree/main/skills/explain
Command: npx skills add https://github.com/drimchansky/agents-kit --skill explain-drimchansky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides clear, structured explanations of code, features, or architecture, adapting the depth and focus to the user's specific question.

Core Features & Use Cases

  • Code Explanation: Detailed walkthroughs of functions, modules, and components.
  • Feature Description: Explanations of user flows, business purpose, and data movement.
  • Architecture Overview: High-level descriptions of system structure, patterns, and integrations.
  • Use Case: When encountering an unfamiliar piece of code, use this Skill to understand its purpose, how it works, and its place within the larger system.

Quick Start

Explain the purpose and functionality of the process_payment function.

Frequently Asked Questions about explain

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

FAQPage Schema
What is the best way to understand unfamiliar code and its architecture?

Understanding unfamiliar code requires tracing calls, checking types, and reviewing tests to reveal data flow. This approach clarifies the purpose of modules and how components integrate within the larger system architecture.

How do I get a detailed walkthrough of a specific function's logic and behavior?

A detailed walkthrough of a specific function involves reading the code and examining documentation to explain its logic. This reveals non-obvious behavior and clarifies how the function processes data.

Can I use code explanation tools to trace data flow across modules?

Yes, code explanation tools trace data flow across modules by gathering context from calls and types. This reveals how data moves through the system and clarifies the business purpose of features.

Does this approach work for high-level architecture overviews or just line-by-line code?

This approach works for both high-level architecture overviews and line-by-line code. It adapts the depth of explanation to your question, covering system structure and patterns or detailed function logic.

When should I not use automated code explanation for debugging?

Automated code explanation should not be used for debugging when you need to fix runtime errors rather than understand purpose. It focuses on explaining non-obvious behavior and architecture, not generating patches.

Why does reviewing tests help explain a feature's purpose?

Reviewing tests helps explain a feature's purpose because tests encode expected behavior and data flow. Examining them alongside code and documentation clarifies the business logic and non-obvious behavior.