code-explainer

Explain code logic by detailing intent, data flow, and key decisions.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Liz2Z/oh-my-skills --skill code-explainer-liz2z
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-explainer
Source: https://github.com/Liz2Z/oh-my-skills/tree/main/skills/code-explainer
Command: npx skills add https://github.com/Liz2Z/oh-my-skills --skill code-explainer-liz2z

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Understanding and documenting complex codebases can be time-consuming and error-prone; this Skill provides structured, easy-to-follow explanations that clarify code intent, architecture, and design decisions.

Core Features & Use Cases

  • High-level overviews that identify purpose, major components, data flow, and patterns.
  • Step-by-step walkthroughs of algorithms and critical functions for onboarding, code reviews, and knowledge transfer.
  • Produce concise, documentation-ready explanations suitable for mentoring, pull requests, or team handoffs.

Quick Start

Explain this code module to a non-technical user with a focus on purpose, main components, and data flow.

Frequently Asked Questions about code-explainer

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

FAQPage Schema
How do I explain complex code logic and architecture to non-technical users?

To explain code logic to non-technical users, generate structured overviews that clarify purpose, major components, and data flow. This approach identifies design decisions and patterns, making complex codebases easy to follow without technical jargon.

What is the best way to document legacy code and its design patterns?

The best way to document legacy code is producing concise, documentation-ready explanations that detail intent and architecture. This process identifies patterns, anti-patterns, and critical functions for effective knowledge transfer and pull requests.

Can I use this to generate walkthroughs of algorithms for code reviews?

Yes, you can generate step-by-step walkthroughs of algorithms and critical functions for code reviews. It applies to diverse languages and frameworks, covering performance considerations and common anti-patterns to ensure thorough review feedback.

Does this approach work with small scripts and large systems across different frameworks?

This approach works with small scripts and large systems across diverse languages and frameworks. It provides high-level overviews identifying major components and data flow, applying to various scales from legacy codebase analysis to mentoring documentation.

Why does my codebase documentation lack details on anti-patterns and performance considerations?

Codebase documentation lacks these details because typical explanations miss key decisions and data flow. Structured code explanations cover typical pitfalls, performance considerations, and common anti-patterns, ensuring documentation captures critical architectural context.