explain

Explain code structure by synthesizing git history, principles, and plan documents.

Updated Mar 25, 2026

Search Tags:#debugging #onboarding #refactoring #code #git-history #explain #architectural-memory

Ready to run

npx skills add https://github.com/Lbstrydom/claude-engineering-skills --skill explain-lbstrydom

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: explain
Source: https://github.com/Lbstrydom/claude-engineering-skills/tree/main/.claude/skills/explain
Command: npx skills add https://github.com/Lbstrydom/claude-engineering-skills --skill explain-lbstrydom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explain why a piece of code is structured the way it is by synthesizing architectural-memory, git history, AGENTS.md/CLAUDE.md principles, and plan documents into a single coherent explanation.

Core Features & Use Cases

Read-only multi-source synthesis that explains code rationale, includes blame/history references, and surfaces plan-driven context.
Onboarding, debugging, and refactoring support by surfacing relevant context and potential risks.

Quick Start

Provide a target file, file:line, or symbol to generate a synthesized explanation of its purpose and history.

Frequently Asked Questions about explain

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

FAQPage Schema

How do I explain why a piece of code is structured the way it is?▼

To explain code rationale, this skill synthesizes git history, plan documents, and architectural-memory into a unified explanation. It targets a file, file:line, or symbol name to present a coherent rationale with references.

What is the best way to understand legacy code logic for onboarding?▼

Understanding legacy code logic for onboarding involves synthesizing git history and architectural-memory. This read-only skill gathers multi-source context to explain code purpose and surface relevant historical discussions.

Can I use git history and plan documents to assess refactoring risks?▼

Yes, you can use git history and plan documents to assess refactoring risks. The skill operates in History mode to surface prior discussions and citations, providing guidance for safe code modifications.

Does this code explanation tool require write access to my repository?▼

No, this code explanation tool is strictly read-only and requires no write access. It safely gathers multi-source context from your repository to present a unified rationale without modifying files.

How do I find prior discussions for a specific symbol or file:line target?▼

To find prior discussions for a specific symbol or file:line target, use History mode. This surfaces citations from architectural-memory, git history, and plan documents, synthesizing them into a coherent explanation.