skills/explain/SKILL.md
Explain code using ASCII diagrams, analogies, and step-by-step walkthroughs. Use when the user asks "how does this work?", "explain this code", "walk me through this", "what does this do?", or "help me understand this".
npx skillsauth add codewithbehnam/cc-docs explainInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
git rev-parse --show-toplevel 2>/dev/null || pwdExplain the code identified by $ARGUMENTS (or the most recently discussed code if no argument is given):
Read the relevant source file(s) fully. Follow imports and dependencies one level deep to understand the full picture.
Identify what the code does at a high level before diving into details.
Structure the explanation as follows:
Compare the code to something from everyday life. A cache is like a sticky note on your monitor. A message queue is like a restaurant ticket rail. Pick the most fitting analogy and explain it in 2-3 sentences.
Draw an ASCII diagram showing the structure, data flow, or component relationships. Use arrows (-->, ==>) to show direction. Keep it under 30 lines. Examples:
Request --> [Auth Middleware] --> [Router] --> [Handler] --> DB
| |
401 Denied [Cache] --> Redis
Walk through the code in execution order, not file order. For each significant step:
One common mistake or misconception about this code that even experienced developers get wrong. Be specific.
List the most important files for understanding this area, with one-line descriptions.
Keep the tone conversational. Prefer short sentences. Avoid jargon unless it is defined. If the target is not found, say so clearly and suggest what the user might look for instead.
tools
macOS GUI automation CLI. Use steer to see the screen, click elements, type text, send hotkeys, scroll, drag, manage windows and apps, run OCR on Electron apps, and wait for UI conditions.
testing
Ship workflow: merge main, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR.
testing
Import cookies from your real browser (Comet, Chrome, Arc, Brave, Edge) into the headless browse session. Opens an interactive picker UI where you select which cookie domains to import. Use before QA testing authenticated pages.
development
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.