Generates a single concrete worked example explaining what a PR, design doc, or plan changes.
npx skills add https://github.com/nvie/skills --skill quick-explainer-nvie
Please help me install this Agent Skill. Skill: quick-explainer Source: https://github.com/nvie/skills/tree/main/skills/quick-explainer Command: npx skills add https://github.com/nvie/skills --skill quick-explainer-nvie
gh), the current branch diff, design docs, Mikado graphs, screenshots, URLs, or pasted text, and treats the diff as the source of truth. - Grounded examples only: Examples come from real bug reports, repro steps, tests, or traced diffs — never invented scenarios — and the Skill says so explicitly when the source cannot support one. - Use Case: You are about to review a teammate's PR you have never seen. Run /quick-explainer <PR URL> and get a 20-line before/after scenario showing exactly what breaks today and what the fix changes. ## Quick Start Run /quick-explainer with a PR link, issue, file path, or nothing to explain the current branch in one concrete before-and-after example.High-intent search queries and answers about installing and using this skill.
Run /quick-explainer with the PR URL or number. It fetches the PR body and diff with gh, treats the diff as the source of truth, and returns a roughly 20-line before-and-after example showing the concrete problem and fix.
Point /quick-explainer at the doc's file path or URL. Instead of a summary, it extracts the problem statement and proposed change, then expresses them as one concrete scenario with a Today and After section.
Yes. Invoke it with no argument and it diffs the current branch against main using the merge base, reads the commit subjects, and builds the explainer from what the branch actually changes.
It accepts GitHub issues, local file paths such as design docs or plans, Mikado graphs, images or screenshots, doc URLs, and pasted text. Each input type has a defined gathering method, and the output shape stays the same.
The Skill never invents a scenario. If the source argues from principle without a real failure, it outputs a one-line statement saying the example cannot be grounded and suggests asking the author what actually broke.
Use it before doing the work, to prime your understanding of what a change is about. It is explicitly not a review — findings, concerns, and nits belong in a separate review pass, and the explainer stops after one example.
Nick777-PixelCreate pull requests from the current branch to canary using git and GitHub CLI.
SkautDevsEnforce a phased development workflow with worktrees, tests, and review for KISSJ changes.
nilbuildCreates guided step-by-step code tours with highlighted code rendered in the browser.
hemoryExplain AI conversation actions, tools, files, and context used.