Explains how code works and why it is built that way in plain language.
npx skills add https://github.com/Sma1lboy/rove --skill teach-sma1lboy
Please help me install this Agent Skill. Skill: teach Source: https://github.com/Sma1lboy/rove/tree/main/.agents/skills/pstack/skills/teach Command: npx skills add https://github.com/Sma1lboy/rove --skill teach-sma1lboy
how and why skills in parallel and weaves their findings into a single plain account, preserving why's confidence hedges. - Audience-aware depth: Picks the few things the person should walk away understanding based on why they are asking, such as reviewing, debugging, or being new to the code. - Progressive visuals: Builds understanding with a series of small diagrams that each add one part, using mermaid for flows and generated whiteboard-style images for spatial ideas. - Use Case: A developer about to modify a virtualization subsystem asks "teach me how this works" and receives a plain explanation of its rendering and disk-loading halves, with diagrams that assemble the flow step by step. ## Quick Start Ask the agent to teach you how a specific subsystem or recent change in this repository works and why it is designed that way.High-intent search queries and answers about installing and using this skill.
Ask for a teaching-style explanation of the subsystem, naming what you want to understand and why. The Skill runs its how and why investigations on the code and returns one plain account covering what it is, how it works, and why it is designed that way.
Request an explanation of the change scoped to your review goal. The Skill reads the diff, investigates the mechanism and the reasoning behind it, and leads with the few points that matter for your review rather than listing every modified function.
No, it only reads and explains code. Its stated goal is that you understand the work, not that anything changes, so it investigates through the how and why skills and returns an explanation.
Yes, it draws mermaid diagrams for flows and structures, and generates whiteboard-style images for spatial ideas like layout or scroll position. For anything with three or more parts it draws a series of small diagrams that each add one element.
Use a scoped question for small changes or when time matters, since the full why investigation is slow. The Skill narrows the why pass by default and widens it only when the reasons behind the design are the point of your question.
MinhThang1009Verify code content and change claims against repository files and git diffs.
cursorExplains code and subsystems plainly by combining how and why skill investigations.
semantica-agiGenerate human-readable explanations for Semantica decisions and graph reasoning.
LbstrydomExplain code structure by synthesizing git history, principles, and plan documents.