mcpField
T
tasks-explain-diff

tasks-explain-diff

github.com/makenotionDevelopment3939 installsUpdated 38w ago
Repository

About tasks-explain-diff

This skill turns code changes into a Notion page covering context, intuition, code walkthrough, verification, and possible alternatives. It is for developers and readers who need to understand a change, and also adds a knowledge quiz through Notion MCP page creation.

Key features

  1. 01Explains change background and intuition
  2. 02Walks through edits by file and line
  3. 03Documents tests and manual verification
  4. 04Presents alternatives with pros and cons
  5. 05Creates a quiz and Notion page

Use cases

  1. 01Document a recent batch of code changes
  2. 02Help new team members understand system edits
  3. 03Record verification steps for code changes
  4. 04Check reader understanding with a quiz

MCP support

Uses Notion MCP to create the explanation page and return its URL.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/makenotion/cursor-notion-plugin --skill tasks-explain-diff

After installing, type/tasks-explain-diffin Claude Code to confirm it loaded.

Details

From the project README

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:
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

Comments

Markdown supported