Explain for Dumb

Explains code changes (branch diff vs master, or uncommitted changes) in plain human language, no scary jargon — so the user understands what an agent (or they) actually changed. Two modes - a "for dummies" story (what was, what happened, how it was done) or a per-file walkthrough. Use when the user says "explain-for-dumb", "explain my changes", "what did the agent do", "walk me through the diff", or wants a plain-language recap of a PR/diff.

11 starsGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)

npx skills add MotleyWildside/explain-for-dumb --skill explain-for-dumb

Manual install

git clone --depth 1 https://github.com/MotleyWildside/explain-for-dumb.git /tmp/explain-for-dumb
mkdir -p ~/.claude/skills
cp -r /tmp/explain-for-dumb/. ~/.claude/skills/explain-for-dumb

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Explain For Dumb

Explain code changes so a person who delegated the implementation (and may not know the codebase deeply) can stay aligned with what now lives in the codebase. The reader is smart but tired — no jargon walls, no line-by-line diff recitals.

The goal is to restore context and understanding, not to replace tests or code review.

**Answer in the language the user is speaking in this session.**

## Step 1 — Decide WHAT to explain (scope)

Run:
- `git branch --show-current`
- `git status --porcelain` (uncommitted = staged + unstaged + untracked)

Then:

1. **On master/main:**
   - Uncommitted changes exist → explain only those.
   - Working tree clean → say there is nothing to explain and stop. Do not invent work.
2. **On a feature branch:**
   - Uncommitted changes exist → **ask the user** (AskUserQuestion): explain the whole branch diff vs master, or only the uncommitted changes.
   - Clean tree → explain the whole branch diff vs master, no question needed.

Getting the branch diff: `git diff $(git merge-base master HEAD)...HEAD` (use `origin/master` if there is no local `master`). For uncommitted: `git diff HEAD` plus untracked files' contents.

## Step 2 — Ask which mode (always ask, AskUserQuestion)

1. **For dummies** — one coherent story, not a file list:
   - **Before:** how things worked / what was broken before.
   - **After:** what works now / what the user-visible outcome is.

Read the full skill on GitHub

Details

Skill name: explain-for-dumb
Repository: MotleyWildside/explain-for-dumb
License: MIT
Repo updated: 1 September 2026

FAQ

What does the Explain for Dumb skill do?

How do I install the Explain for Dumb skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add MotleyWildside/explain-for-dumb --skill explain-for-dumb. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Explain for Dumb popular?

It lives in MotleyWildside/explain-for-dumb, which has 11 GitHub stars and 0 forks.

Related skills

Commit Daily Summary

leonsong09/commit-daily-summary

Use when the user wants a same-day summary of git commits or a commit-based daily report, asks what they did today, or says 总结我今天做了什么, 总结我的提交, 提交总结, 今天提交总结, 日报.

Git & Code Review

Nb

Alan-Youngzhe/noob2builder

Noob2Builder AI Builder School——由 Agent 在主对话中带学的全选修课程，从电脑与 AI 基础、Git/GitHub、Builder 工作法，到做出并发布第一个可验收作品、测试与验证、前后端工程基础（HTML/CSS/JS、npm、Vite、TypeScript、Vue、React、组件化、TSX、路由、项目结构、API、鉴权与部署）、Agent 构建和 Agentic Engineering。适用于纯小白或已有项目的学习者提出“带我学 AI”“我想做第一个作品”“教我 Git/GitHub”“教我单元测试、集成测试、冒烟测试或 E2E”“教我前端/后端”“看不懂 Agent 生成的网页代码”“什么是 token/context/Agent/MCP/Skill”“教我构建 Agent”“从 vibe coding 进阶”“继续上次课程”等请求；支持按目标选课、动态插入共享知识、真实实操、本地学习存档和证据卡。

Git & Code Review

Github Profile Readme

boffti/github-profile-readme

Create or upgrade a GitHub *profile* README — the special README.md in the repo named exactly after a username (github.com/<user>/<user>) that renders at the top of the profile page. Use this whenever someone wants to make, design, redesign, refresh, or "level up" their GitHub profile, set up their github.com/<user>/<user> repo, add stats cards / badges / a tech stack / an auto-updating blog feed to their profile, or asks "how do I get that box on my GitHub page." Trigger even when they don't say the word "README" — "make my GitHub look good", "personalize my GitHub", or "set up my dev profile

Git & Code Review

Gh Actions

retlehs/gh-actions

GitHub Actions best practices — current action versions, caching, security, and common patterns. Activate when writing or modifying GitHub Actions workflows.

Git & Code Review

Gh Fetch

retlehs/gh-fetch

Use the GitHub CLI to fetch content from GitHub URLs instead of web fetching. Activate when the user shares a GitHub issue, PR, repo, or discussion link.

Git & Code Review

Recat Web

0xtbug/Recat

Automatically install and set up the Recat website from github.com/0xtbug/Recat, including prerequisites, dependencies, local password, findings folder, build, and server startup. Also use to repair or develop an existing Recat installation.

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.