teach

Generate structured markdown documentation by tracing code execution paths and dependencies.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/Theycallmeholla/skills --skill teach-theycallmeholla
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teach
Source: https://github.com/Theycallmeholla/skills/tree/main/skills/teach
Command: npx skills add https://github.com/Theycallmeholla/skills --skill teach-theycallmeholla

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of tribal knowledge and undocumented code by automatically generating structured, developer-facing documentation for any feature or module in your codebase.

Core Features & Use Cases

  • Automated Documentation: Traces execution flow, data movement, and dependencies to explain complex logic.
  • Debugging Support: Provides a "Where to look if something breaks" section for every documented feature.
  • Use Case: When a new developer joins the team, use this skill to generate a comprehensive walkthrough of the authentication middleware or payment processing flow to accelerate their onboarding.

Quick Start

Ask the AI to teach you how the payment processing module works by referencing the relevant files in the src directory.

Frequently Asked Questions about teach

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

FAQPage Schema
How do I automatically generate documentation for an existing codebase?

You can generate documentation for an existing codebase by tracing execution paths, data flow, and dependencies to automatically produce structured, developer-facing markdown references.

What is the best way to explain complex code execution flow to new developers?

To explain complex code execution flow to new developers, generate detailed architectural walkthroughs that trace data movement and dependencies to accelerate feature onboarding.

Can I assess technical debt by analyzing file structures and route logic?

Yes, you can assess technical debt by analyzing file structures, function definitions, and route logic to map dependencies and generate comprehensive system architecture explanations.

How do I create a debugging guide for undocumented module dependencies?

To create a debugging guide for undocumented module dependencies, trace execution paths and data flow to automatically generate a 'Where to look if something breaks' section for every documented feature.

Does this documentation tool work without accessing internal source files?

No, this documentation tool requires codebase access to analyze file structures, function definitions, and route logic, meaning it cannot generate accurate execution flow references without internal source file access.

When do I need to generate structured markdown references for system architecture?

You need to generate structured markdown references for system architecture when onboarding new developers, assessing technical debt, or eliminating tribal knowledge surrounding undocumented feature modules.