pr-explainer-quiz
/pr-explainer-quiz
Wyjaśnia pull request lub zakres commitów recenzentowi: co się zmieniło, dlaczego, z diagramem Mermaid, a potem sprawdza zrozumienie quizem.
- Autor
- Avr8 ↗
- Repozytorium
- claude-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 11.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 17
- Skrypty
- 2
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 11.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 2 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: evals/explains-diff-then-quizzes/place-files.sh, evals/skip-quiz-when-asked/place-files.sh
Co robi i kiedy
Wyjaśnia pull request lub zakres commitów recenzentowi: co się zmieniło, dlaczego, z diagramem Mermaid, a potem sprawdza zrozumienie quizem.
Wyzwalacze z opisu
Oryginalny opis (EN)
Explain a pull request, diff, commit range or branch to a human reviewer — what changed, why, how data/control flows now, with a Mermaid diagram — then run a short interactive quiz to check they actually understood it before approving. Use whenever someone asks "explain this PR", "walk me through this diff", "help me review", "what does this change do", wants to onboard onto a teammate's change, or worries they're rubber-stamping AI-written code they don't understand.
Jak działa
- 1. Gather the change
- 2. Explain — in this order
- 3. Quiz
- 4. Wrap up
- Scope to the request
Podgląd SKILL.md
---
name: pr-explainer-quiz
description: Explain a pull request, diff, commit range or branch to a human reviewer — what changed, why, how data/control flows now, with a Mermaid diagram — then run a short interactive quiz to check they actually understood it before approving. Use whenever someone asks "explain this PR", "walk me through this diff", "help me review", "what does this change do", wants to onboard onto a teammate's change, or worries they're rubber-stamping AI-written code they don't understand.
---
# PR explainer + comprehension quiz
AI-assisted coding makes it easy to approve code you never really understood. This skill explains a change at the level a reviewer needs, then checks understanding with a few pointed questions — so "LGTM" means something.
## 1. Gather the change
Pick whichever applies:
```bash
gh pr view <num> --json title,body,baseRefName,headRefName,files # GitHub PR
gh pr diff <num>
git diff <base>...<head> # branch
git show <sha> # single commit
```
Read the PR description and linked issue if any. Then read the **surrounding code** of changed functions (callers, callees, tests) — a diff alone hides the context that matters.
## 2. Explain — in this order
1. **One-paragraph summary**: what behaviour changes for a user or caller. Not a list of files.
2. **Why**: the problem being solved, from the description/issue/commit messages. If the reason isn't stated anywhere, say so — that's a review finding.
3. **Diagram**: a Mermaid `sequenceDiagram` or `flowchart` of the *new* flow, highlighting what's new/changed (use a note or `:::changed` class). Keep it under ~15 nodes; diagram the core path, not everything.
4. **Walkthrough by concept, not by file**: group related hunks ("the retry logic", "the new config flag"). For each: what it does, and anything non-obvious (concurrency, error handling, edge cases, performance).
5. **Risk notes**: things a reviewer should look at hardest — changed public interfaces, migrations, deleted tests, error paths swallowed, security-sensitive code, missing tests for new branches. Be specific with `file:line`.
## 3. Quiz
Ask **3–5 questions**, one at a time, waiting for the answer before the next. Good questions require understanding, not recall:
- "What happens now if `<dependency>` times out during `<operation>`?"
- "Which existing caller is affected by the signature change, and how?"
- "Why does `<line>` need to come before `<line>`?"
- "If we roll this back after the migration ran, what breaks?"
Avoid trivia ("what's the new function called?"). Mix: at least one about failure/edge behaviour, one about why a design choice was made.
After each answer: say whether it's right, and give the correct explanation in 1–3 sentences with a code reference. If they're wrong on something important, suggest which part of the diff to re-read.
## 4. Wrap up
Score (e.g. 4/5) and a short verdict: "ready to review", or "re-read X before approving". Offer to draft review comments for any risks found.
## Scope to the request
The full flow (summary → why → diagram → walkthrough → risks → quiz) is the default for "walk me through this" or "help me review". When the user narrows the request, respect it:
- "no quiz" / "skip the quiz": steps 1–2 without step 3.
- "just the summary and risks": the one-paragraph summary and the risk notes, nothing else: no diagram, no walkthrough. Offer the rest in one closing line.
- "just the diagram": the diagram plus a two-sentence caption.
The first risk listed should be the one that changes behaviour for users or money (like a silent wrong charge), not the most technically interesting one.
Pliki w paczce (17)
- SKILL.md 4 KB
- evals/explains-diff-then-quizzes/case.yaml 1 KB
- evals/explains-diff-then-quizzes/place-files.sh 1 KB
- evals/explains-diff-then-quizzes/prompt.md 1 KB
- evals/explains-diff-then-quizzes/files/change.diff 1 KB
- evals/explains-diff-then-quizzes/graders/01-the-response-includes-a-mermaid.md 1 KB
- evals/explains-diff-then-quizzes/graders/02-the-silent-0-charge-is.md 1 KB
- evals/explains-diff-then-quizzes/graders/03-the-response-asks-exactly-one.md 1 KB
- evals/explains-diff-then-quizzes/graders/04-the-response-does-not-reveal.md 1 KB
- evals/skip-quiz-when-asked/case.yaml 1 KB
- evals/skip-quiz-when-asked/place-files.sh 1 KB
- evals/skip-quiz-when-asked/prompt.md 1 KB
- evals/skip-quiz-when-asked/files/change.diff 1 KB
- evals/skip-quiz-when-asked/graders/01-the-response-asks-no-quiz.md 1 KB
- evals/skip-quiz-when-asked/graders/02-the-response-contains-only-a.md 1 KB
- evals/skip-quiz-when-asked/graders/03-the-first-risk-listed-is.md 1 KB
- evals/skip-quiz-when-asked/graders/04-the-summary-is-at-most.md 1 KB
Wersje
W bazie nie ma innych skilli o nazwie pr-explainer-quiz.
Migawka bazy z 13.11.2026 · wersja paczki 024aef0fcfc6 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100diff-visual
Przygotowuje do przeglądu zmiany w git: opisuje kontekst systemu i ideę zmiany, pokazuje diff z komentarzem oraz układa quiz z pięciu pytań. - 100explain-diff
Tworzy bogaty samodzielny wyjaśniacz HTML zmiany w kodzie: tło, intuicja z diagramami, przewodnik po kodzie i interaktywny quiz. - 100explain-diff
Wyjaśnia zmianę kodu, diff, gałąź, commit lub PR jako bogatą samodzielną stronę: tło, intuicję z przykładami, przejście w porządku wykonania, co może się zepsuć i quiz sprawdzający zrozumienie. - 95explain-diff-html
Tworzy interaktywne, samodzielne wyjaśnienie zmian w diffie lub gałęzi w HTML, z tłem, intuicją, przejściem po kodzie i quizem. - 84explain-change
Tworzy omówienie pull requesta w markdownie: powód, stan przed i po, mapa ryzyka, opisane hunki i opcjonalny quiz, z opcjonalnym widokiem interaktywnym. - 100explain
Wyjaśnia pull request, gałąź albo bieżący diff jako interaktywny przegląd od ogółu do szczegółów, po jednej części naraz.