change-quiz
After a working session, produce a report on what changed plus a quiz the user must pass before merging. Use when the user asks "what did we actually do," wants to review a large change, or invokes a quiz before merge.
npx skills add Neeeophytee/finding-unknowns-skills --skill change-quiz --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Change quiz After a long session the agent has often done more than the user realizes, and a diff only shows surface. Behavior lives in how the change interacts with existing code paths. The user should merge only what they can pass a quiz on. ## Steps 1. Build the report first, in four short sections: - **Context** — what problem this session set out to solve. - **What changed** — grouped by intent (feature, fix, refactor), not by file. - **How it interacts** — the existing code paths the change touches, and what now behaves differently even in files the diff doesn't show. - **Intuition** — the 2-3 mental-model updates the user should walk away with ("retries are now idempotent because X"). 2. For long sessions, offer the report as a single self-contained HTML page with the quiz at the bottom — it reads better than a wall of markdown. 3. Then the quiz: 5-8 questions targeting what would bite an unaware maintainer. - Mix recall ("what happens to in-flight jobs during deploy now?") with prediction ("if someone calls X with a stale token, what do they see?"). - Weight questions toward deviations, edge cases, and interaction effects — not trivia about names. 4. Grade honestly, one r
- Steps
- Guardrails
What does the change-quiz skill do?
After a working session, produce a report on what changed plus a quiz the user must pass before merging. Use when the user asks "what did we actually do," wants to review a large change, or invokes a quiz before merge.
How do I install it?
Run `npx skills add Neeeophytee/finding-unknowns-skills --skill change-quiz --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Neeeophytee/finding-unknowns-skills, a repository with 298 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
