Skip to content

JPeetz/agent-skills / skills/development/finding-unknowns/skills/change-quiz

change-quiz

Verified

Use when reviewing what changed after a long session before merging — build a change report grouped by intent, then quiz the user so unread changes don't ship.

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 round at a time. For each miss, explain the right answer AND flag it: a miss is either a gap in the user's model or a sign the change is too clever — say which.
  5. Pass = merge-ready. Fail = point back to the specific report sections to reread, then offer a fresh variant quiz. Do not soften the bar; the whole point is that unread changes don't ship.

Guardrails

  • Do not silently pass a quiz that was barely passed. If the user got 5/8 but the misses were on critical interactions, that is a fail.
  • Keep quiz language neutral and factual. The purpose is understanding, not shaming.
  • If the session produced no meaningful changes (e.g., research-only), say so — don't fabricate a quiz.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall