Quizzing code

Skill UniversalAvenue/quizzing-code

Quizzes developers about their code changes before PR review. Analyzes git diff, asks probing questions with code snippets, tracks discoveries, and generates a summary report. Use when user says "quiz me", "code quiz", wants self-review, or before requesting PR review.From its SKILL.md

Install

npx -y skills add UniversalAvenue/quizzing-code

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.7 KB, 370 tokens by cl100k_base, as published. Nobody here has run it

Code Comprehension Quiz

Interactive self-review that helps catch issues before reviewers do.

Workflow

Copy this checklist and track progress:

Quiz Progress:
- [ ] Step 1: Analyze branch diff
- [ ] Step 2: Identify quiz topics (3-8 questions)
- [ ] Step 3: Ask questions one at a time
- [ ] Step 4: Track discoveries
- [ ] Step 5: Generate summary report

Step 1: Analyze Changes

BASE="${ARGUMENTS:-main}"
git diff $BASE...HEAD --stat
git diff $BASE...HEAD

Read changed files for full context when needed.

Step 2: Identify Topics

Find significant changes to quiz about:

Database: tables, columns, constraints, triggers
API: endpoints, request/response shapes
Logic: new functions, state changes, algorithms
Types: interfaces, type definitions

Step 3: Ask Questions

One question at a time. Format:

**Question N/M** - [Category]

Looking at `path/file.ts:45-52`:
\`\`\`
[5-15 lines of relevant code]
\`\`\`

[Probing question]

Question types - see QUESTIONS.md

Step 4: Track Discoveries

Categorize findings as:

Critical: Bugs, data loss risks, security issues
Important: Design gaps, missing edge cases
Minor: Style, naming, small improvements

Step 5: Generate Summary

Save to .claude/quiz-summaries/YYYY-MM-DD-branch-name.md

Template - see SUMMARY_TEMPLATE.md

What ships with it: 3 files

5.1 KB alongside SKILL.md

references/

QUESTIONS.md1.2 KB
SUMMARY_TEMPLATE.md1.6 KB

README.md2.4 KB