What problem does it solve? Understanding a code change, diff, branch, or pull request often requires digging through surrounding code, tests, and documentation, and sharing that understanding with a team means writing it up manually. This Skill investigates the change and its surrounding system, then publishes a structured teaching page to Notion via the Notion MCP tools. ## Core Features & Use Cases - System-Aware Explanation: Explores surrounding code, tests, callers, and data models to explain behavior, not just file-by-file edits. - Structured Page Format: Produces Background, Intuition, Code, and Quiz sections with Notion-native diagrams, callouts, and toggle-based multiple-choice questions. - Prompt-Injection Defense: Treats diffs, PR metadata, and commit messages as untrusted data and ignores any instructions embedded in them. - Use Case: After opening a pull request that refactors a data pipeline, ask for an explanation page and receive a Notion URL your teammates can read to understand the motivation, mental model, implementation flow, and edge cases, then self-test with five quiz questions. ## Quick Start Explain the changes on my current branch as a Notion page using the explain-diff-notion skill and return the page URL.
