MaybeMonad Change Quiz
Use this skill when the user wants to understand a completed change deeply enough to review, merge, or hand it off. The quiz should test behavior and risk, not trivia.
Workflow
- Inspect the actual change:
- Diff, touched files, tests, runtime checks, implementation notes, and relevant existing code paths.
- Explain the change:
- Problem, previous behavior, new behavior, important files, data flow, edge cases, validation, and residual risk.
- Build intuition:
- Explain why the implementation works in the local architecture.
- Call out non-obvious dependencies and failure modes.
- Create the quiz:
- Ask 5-10 questions depending on change size.
- Prioritize behavior, tradeoffs, risk, and validation.
- Include scenario questions, not just recall questions.
- Hold the answer key unless the user asks for a self-study version.
- Grade the user's answers against the behavior that actually shipped.
Report Shape
- Context.
- What changed.
- How it works.
- Files and code paths.
- Verification.
- Residual risks.
- Quiz.
Rules
- Do not quiz on filenames unless the path matters to understanding behavior.
- Do not claim the user passed unless their answer covers the real risks.
- If verification is incomplete, include that in both the report and quiz.
- If the user fails, explain the gap and ask a follow-up question on that gap.