Explains code changes and subsystems through progressive diagrams and plain-language walkthroughs.
npx skills add https://github.com/lucasheriques/pstack --skill teach-lucasheriques
Please help me install this Agent Skill. Skill: teach Source: https://github.com/lucasheriques/pstack/tree/main/skills/teach Command: npx skills add https://github.com/lucasheriques/pstack --skill teach-lucasheriques
how and why skills in parallel and weaves their findings into one coherent explanation, preserving confidence hedges from the why investigation. - Progressive diagram teaching: Builds understanding diagram by diagram, adding one part at a time using mermaid, SVG, or ASCII sketches instead of a single dense figure. - Audience-adapted depth: Calibrates what to explain based on why the person is asking (about to change it, reviewing it, debugging it, new to it) and what they already know. - Use Case: A developer joining a team asks "teach me the new sync engine" and receives a plain definition, a step-by-step walkthrough of the data flow with incremental diagrams, and the design rationale, with offers to go deeper on any thread. ## Quick Start Ask the assistant to teach you a specific change or subsystem, for example: teach me how the authentication migration works and why it was designed this way.High-intent search queries and answers about installing and using this skill.
Ask to be taught the subsystem by name, such as "teach me the sync engine". The Skill runs code walkthrough and design-rationale analysis, then delivers a plain explanation with diagrams built up one part at a time.
Request a teaching pass on the change or pull request. The explanation leads with what the change is, walks through how it works step by step, and covers why it was built that way, so you can review with real context.
No. The goal is understanding, not changes. It reads code, diffs, and history to build the explanation, and may open the code or debugger to show you, but it does not edit anything.
It uses mermaid for flows and structures where labels carry the meaning, and SVG or ASCII sketches for spatial ideas like layout or scroll position. Complex systems are drawn as a series, adding one part per diagram.
Use it when you need working understanding fast: joining a new area, preparing to modify or debug something, or reviewing an unfamiliar change. It compresses the code reading and design-history digging into one paced account.
remix-runReview Remix pull requests from a local checkout for correctness and security.
cursorExplains code and subsystems plainly by combining how and why skill investigations.
arndvsReviews staged or recent git diffs to find edge cases, logic errors, and integration risks before merging.
MrPointerDocument system architecture with layer boundaries, communication patterns, and design rationale.