renzrollon/interlock/explain-code

Claude Code and agent skill by renzrollon/interlock

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Explain code to a beginner in that stack — either a module walkthrough (what each function does, how calls link, where data flows, which patterns recur) or a commit teach-in (why each file changed, what changed, blast radius, what would break if it were left out). Use when asked to explain code, walk through a directory, or explain the last commit.

Install

npx vskill@latest install renzrollon/interlock/explain-code

SKILL.md

Teach code to someone new to this stack. Not reviewing, not judging — teaching.

Calibrate to a reader who knows programming fundamentals but is new to this project's language and framework. Explain the idioms that stack takes for granted, one short aside each. Do not explain what a function is.

Modes

ModeWhenLoad
Module walkthrough (default)A file or directory is named, or the user asks how an area works${CLAUDE_SKILL_DIR}/module-walkthrough.md
Commit teach-inLast commit, a hash or range, "what changed", --commit / --commits N${CLAUDE_SKILL_DIR}/commit-teachin.md

When ambiguous, prefer the module walkthrough unless the user mentioned a commit or "what changed".

After choosing a mode, read the matching sibling file and follow it for steps, structure, and output format. This file only routes.

Output path

Resolve the destination before writing. Both modes use the same rule:

SituationWrite to
Scoped to an OpenSpec change — a change name was passed, or one resolves via openspec status --jsonopenspec/changes/<change-name>/code-explanation.md
No change context (ad-hoc walkthrough)docs/CODE_EXPLANATION.md

Do not "simplify" this back to a single path. A change-scoped explanation belongs beside manual-test-plan.md in its own change directory. Writing every run to docs/CODE_EXPLANATION.md overwrites the previous change's explanation — and because docs/ is the corpus /interlock:docs-digest indexes, each rewrite permanently marks .claude/graph/DOCS_DIGEST.md stale through its source_hashes.

Shared rules

  • Single agent, no fan-out. Understanding builds sequentially; parallel investigators produce four disconnected fragments, which is the opposite of a walkthrough.
  • Write the full explanation to the resolved path (overwrite), then tell the user the file is ready with a 5–10 line summary.
  • Pull domain context on demand: .claude/graph/DOCS_DIGEST.md first, then interlock-graph context / docs. Never preload all of docs/ — see ${CLAUDE_PLUGIN_ROOT}/shared/TOOL-ECONOMY.md Rule 0.5.

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

See the full security report

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

See evaluation results

Source

Popularity

7-day trend score
0

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/renzrollon/interlock/explain-code/badge)](https://verified-skill.com/skills/renzrollon/interlock/explain-code)

Something wrong with this skill or its page? Tell us.