菜单
Explains code in plain language for someone unfamiliar with the programming language. Use when asked to explain code, walk through logic, describe what a function does, or when the user says "explain this" or "walk me through this".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/davila7/claude-with-skills --skill explain-code命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Summarizes uncommitted git changes in a concise machine-readable format. Use in CI pipelines, scripts, or headless invocations where the output will be piped or captured.
Explains what a skill is and demonstrates that skills are working. Use when testing skills, when asked about skills, or when asked to demonstrate how skills work.
Demonstrates the personal scope for Claude Code skills. Use when testing personal-scoped skills or when the user wants to understand the difference between personal and project skill scopes.
基于 SOC 职业分类
正在显示 SKILL.md
| title | explain-code |
| name | explain-code |
| description | Explains code in plain language for someone unfamiliar with the programming language. Use when asked to explain code, walk through logic, describe what a function does, or when the user says "explain this" or "walk me through this". |
Identify the code to explain. In order of priority:
Identify the programming language. Do not assume from the file extension alone — check the syntax if the extension is missing or ambiguous.
Explain the code in plain language covering these three areas:
Overall purpose — What does this code do? What problem does it solve or what action does it perform? State this in one or two sentences without using the function or variable names as a substitute for explanation.
Main data flow — How does data move through the code? What comes in, what happens to it, and what comes out? For a function: inputs, transformations, output. For a class: how instances are created and how their state changes. For a script: what it reads, what it produces.
Non-obvious logic — Is there any behavior that would surprise a competent programmer reading this for the first time? Flag things like: side effects, error suppression, hardcoded assumptions, subtle timing dependencies, or clever bitwise operations.
Use an analogy if it genuinely makes the concept clearer. Do not force one if the code is self-explanatory once described directly.
Limit the explanation to what was asked. If the user pointed to one function, explain that function. Do not expand to the surrounding architecture unless asked.
Do not restate the obvious. If a function is named calculateTax and it calculates tax, skip the sentence saying "this function calculates tax" and go directly to how it does it.
