skills.rest
bilgrami
bilgramiCOMMUNITY
Explore all skills by this author →
Website𝕏@sbilgramiGitHub

explain

Explain code logic, architecture, and data flow for onboarding and reviews.

Updated Aug 23, 2026
Search Tags:#architecture#debugging#documentation#onboarding#code#explain#execution-flow
One-click install
npx skills add https://github.com/bilgrami/corporate-agent --skill explain-bilgrami
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: explain
Source: https://github.com/bilgrami/corporate-agent/tree/main/skills/explain
Command: npx skills add https://github.com/bilgrami/corporate-agent --skill explain-bilgrami

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers understand and communicate how a codebase works by providing structured, thorough explanations of code logic, architecture, and behavior.

Core Features & Use Cases

  • Clear, structured explanations of code components and execution flow
  • Multi-level guidance for beginner to advanced readers
  • Comprehensive walkthroughs with architecture diagrams or ASCII where helpful
  • Use cases include onboarding new contributors, code reviews, and design decision justification

Quick Start

Provide a clear, multi-level explanation of the given codebase by walking through its execution flow and design decisions.

Frequently Asked Questions about explain

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

FAQPage Schema
How do I explain code architecture and execution flow for developer onboarding?▼

To explain code architecture for onboarding, detail the execution flow, entry points, and component relationships. This structured approach clarifies data flow and edge cases, helping new developers understand the codebase without altering runtime behavior.

What is the best way to document code logic and component relationships for a review?▼

The best way to document code logic for reviews is using structured, multi-level explanations that cover execution flow and design decisions. This descriptive method details component relationships thoroughly, justifying architecture choices without guiding runtime modifications.

Can I generate architecture walkthroughs that cover edge cases and data flow for my project?▼

Yes, you can generate architecture walkthroughs that cover edge cases and data flow. By detailing component relationships and entry points, the explanation remains strictly descriptive and structured, providing comprehensive guidance for varying developer skill levels.

Does this approach provide multi-level explanations for both beginners and advanced developers?▼

Yes, this approach provides multi-level explanations for both beginners and advanced developers. It breaks down execution flow, architecture, and design decisions comprehensively, ensuring clear onboarding and effective code reviews across different expertise levels.

Why should I use structured code explanations instead of modifying code to understand it?▼

You should use structured code explanations because they remain strictly descriptive, detailing logic and data flow without altering runtime behavior. This prevents unintended side effects while thoroughly documenting architecture and edge cases for onboarding and reviews.

Related Skills

Explore More Software Engineering Skills→
ncsound919ncsound919

security-threat-model

Identify and document repository-specific threat models for defensive security.

Community
Advanced
vikisingh23vikisingh23
4

documentation

Generate API references, architecture diagrams, and onboarding guides from code and OpenAPI specs.

Community
Intermediate
yun520-1yun520-1
38

code-analyzer

Analyze codebases for architectural patterns, code quality, and DDD elements.

Community
Advanced
backengineeringbackengineering
434

dynamic-instrumentation

Instrument binaries and trace runtime behavior using LLVM infrastructure.

Official
Advanced