resonance-ops-explain

Generates concrete explainers of concepts, diffs, and recent work for the developer.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/manusco/wolfgang --skill resonance-ops-explain-manusco
Or copy as Structured Prompt for Agentâ–¼
Please help me install this Agent Skill.
Skill: resonance-ops-explain
Source: https://github.com/manusco/wolfgang/tree/main/.agents/skills/ops/explain
Command: npx skills add https://github.com/manusco/wolfgang --skill resonance-ops-explain-manusco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When an AI agent writes the code, the human operator stops building the mental model that writing by hand used to provide. This Skill produces dense, repo-grounded explainers so the developer keeps understanding what was built and can make the next decision themselves. ## Core Features & Use Cases - Four explainer modes: teach a concept new to the codebase, walk a diff or PR by intent, make an idea or plan legible, or reconstruct a window of recent work. - Reader-targeted writing: names the reader's level and existing knowledge, grounds every claim in real files, functions, and numbers from the actual repo, and teaches one load-bearing idea per explainer. - Optional active recall check-in: offers predict-then-reveal or checked exercises where the prediction is always collected before any explanation is revealed. - Use Case: After the agent adds a background job queue, ask for an explanation and receive a concrete walkthrough of the actual queue code, plus an optional quiz question that tests whether you can predict its behavior before seeing the answer. ## Quick Start Ask the agent to explain how the new background job queue works, noting that you are comfortable with the app but new to queues.

Frequently Asked Questions about resonance-ops-explain

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

FAQPage Schema
How do I get an explanation of code an AI agent wrote for me?â–¼

Ask the agent to explain the concept, diff, or recent work and state your experience level. The explainer is grounded in the actual files, functions, and numbers from your repo rather than a generic textbook description, and focuses on one load-bearing idea.

What is a predict-then-reveal check-in for learning code changes?â–¼

Predict-then-reveal shows you only the raw change and asks one specific question about what it does, then ends the turn. The explanation is revealed only after you commit to a prediction, which builds recall instead of passive recognition.

Can I get the explanation and the quiz answer in the same message?â–¼

No. The check-in is all-or-nothing: either the prediction is collected before any reveal, or you receive a plain explainer with no quiz. Showing the question and answer together would turn recall into recognition and teach nothing.

When should I skip the active recall check-in?â–¼

Skip it for throwaway fixes or one-time context dumps you will not need again. Offer it only when the material is worth retaining, such as a concept the codebase now depends on or a decision you will have to defend.

What are the limitations of an AI-generated code explainer?â–¼

An explainer fails if it is generic enough to have been written without opening the repo, or if it tries to tour the whole system. It teaches one load-bearing idea per explainer and deliberately names what it leaves out when the subject is too large.