# tasks-explain-diff

Generate a rich Notion document explaining code changes. Creates comprehensive documentation with background, intuition, code walkthrough, and verification steps.

Skill by Notion. Category: Documents.

## Install

Project (for this project only):

```sh
npx skills add makenotion/cursor-notion-plugin --skill tasks-explain-diff
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

Global (for every project on this machine):

```sh
npx skills add makenotion/cursor-notion-plugin --skill tasks-explain-diff -g
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

## Tags

- Runs on your computer: It runs as a program on your machine, with your access.

## Security audits

- Gen Agent Trust Hub: Pass
- Socket: Pass
- Snyk: Pass
- Runlayer: Pass
- ZeroLeaks: Pass

Installs: 35. Installs counted by skills.sh. [Open on skills.sh](https://www.skills.sh/makenotion/cursor-notion-plugin/tasks-explain-diff)

## Source

[Open the source](https://github.com/makenotion/cursor-notion-plugin/tree/HEAD/skills/tasks-explain-diff). Checked 2026-10-10. This summary may contain AI-generated text, so it can be wrong. Check the source before you rely on it.

## SKILL.md

````markdown
---
name: tasks-explain-diff
description: Generate a rich Notion document explaining code changes. Creates comprehensive documentation with background, intuition, code walkthrough, and verification steps.
---

# Explain Code Changes

Create a rich explanation of code changes as a new Notion page.

## Input

The user will point to code changes to explain. If not explicitly specified, explain the most recent batch of changes made in the conversation.

## Document Sections

### Background

Explain the existing system relevant to this change:
- Broadly explore surrounding code for context
- Include deep background for beginners (can be skipped by familiar readers)
- Provide narrow background directly relevant to the change

### Intuition

Explain the core intuition for the code change:
- Focus on the essence, not full details
- Use concrete examples with toy data
- Use figures and mermaid diagrams liberally

### Code

High-level walkthrough of the changes:
- Group and order changes in an understandable way
- Explain the purpose of each significant change
- Link to specific files and line numbers

### Verification

Explain how the code change was verified:
- Unit tests, integration tests, etc.
- Step-by-step guide for manual QA

### Alternatives

Describe 1-2 alternative approaches (if identifiable):
- Each alternative includes pros and cons
- Layout pros/cons in 2 columns
- Only include if it represents an orthogonal approach
- Omit this section if no meaningful alternatives exist

### Quiz

5 questions testing reader's knowledge:
- Medium difficulty - requires understanding the substance
- Multiple choice with explanations
- Use toggle blocks for answers:

```markdown
1. Question
   > Option 1
     - Explanation for why incorrect
   > Option 2
     - Explanation for why correct
```

## Formatting Guidelines

- Use the Notion MCP to create the page and return its URL
- Write with clarity and flow - engaging, classic style
- Smooth transitions between sections
- Use consistent diagram families throughout
- Include callouts for key concepts, definitions, and edge cases
````

- Previous: [tasks-build](https://syn4pse.dev/terminal/notion-tasks-build.md)
- Next: [create-page](https://syn4pse.dev/terminal/notion-create-page.md)
- [Terminal](https://syn4pse.dev/terminal.md)
- [Suggest a change](mailto:terminal@syn4pse.dev?subject=Terminal%20suggestion)
