explain

Explain code targets with repository references and call-chain context.

139|20|Updated Jul 5, 2025

Search Tags:#architecture #debugging #repository #code #code-review #explain #symbol

Ready to run

npx skills add https://github.com/penwyp/ClaudePreference --skill explain-penwyp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: explain
Source: https://github.com/penwyp/ClaudePreference/tree/main/skills/explain
Command: npx skills add https://github.com/penwyp/ClaudePreference --skill explain-penwyp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explain targets in repository context against local code to reveal their role, call paths, ownership, inputs, outputs, and dependencies, enabling developers to understand code structure without guessing.

Core Features & Use Cases

Explain code snippets, files, or symbols by locating them in the repository and detailing their purpose, relationships, and impact on the call graph.
Clarify how a function, class, or config participates in architecture, showing upstream inputs and downstream effects.
Use evidence from the codebase, citing where the target is defined and used, and highlighting key parameters, flags, or return values.

Quick Start

Explain the given target in the repository context, highlighting its role, inputs, outputs, and where it fits in the call chain.

Frequently Asked Questions about explain

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

FAQPage Schema

How do I explain what a code symbol does in the context of my repository?▼

To explain a code symbol in repository context, the Skill locates the target within the local codebase to detail its purpose, call paths, ownership, inputs, outputs, and dependencies using concrete evidence from where it is defined and used.

What is the best way to understand how a function participates in the overall architecture?▼

Understanding how a function participates in architecture involves identifying upstream inputs and downstream effects on the call graph. The Skill resolves ambiguity by locating best matches and presenting findings with concrete repository references.

Can I use this to explain code snippets and configuration files, not just functions?▼

Yes, you can explain code snippets, files, symbols, or configurations. The approach applies to any target by locating the best match in the codebase and detailing its role, relationships, and impact on the call graph.

How do I trace the call chain and downstream effects of a specific class in my codebase?▼

Tracing the call chain of a class requires locating it in the repository to articulate its behavior and downstream effects. The Skill connects the target to the surrounding call chain, highlighting key parameters, flags, and return values.

Does this approach work for resolving ambiguity when multiple code matches exist?▼

Yes, resolving ambiguity is handled by prioritizing relevant parameters and locating best matches in the codebase. The Skill explains the target's role with concrete evidence, ensuring clarity without guessing the code structure.