Diff Intake
Reads a PR or branch diff and produces a structured YAML change brief for downstream analytics instrumentation skills. Use this as the first step whenever a user shares a PR link, branch comparison, or raw diff and wants to understand what changed, what needs tracking, or how to instrument a feature. Trigger on phrases like "review this PR", "what changed in this branch", "help me instrument this diff", "check analytics coverage for this change", or any request to start the analytics review workflow.
Install
/plugin marketplace add amplitude/mcp-marketplaceThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add amplitude/mcp-marketplace --skill diff-intakegit clone --depth 1 https://github.com/amplitude/mcp-marketplace.git /tmp/mcp-marketplace
mkdir -p ~/.claude/skills
cp -r /tmp/mcp-marketplace/plugins/amplitude/skills/diff-intake ~/.claude/skills/diff-intakePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# diff-intake Follow this skill step by step. You are step 1 of the analytics instrumentation workflow. Produce a compact YAML change brief that downstream skills (discover-event-surfaces, instrument-events) will consume. Keep the output machine-readable and precise — no prose around the YAML block. ## Step 1: Gather changed files and categorize Fetch the list of changed files from the source, then categorize each one. ### Fetching changes - **PR URL** `gh pr view <number-or-url>` `gh pr view <pr-number> --json files --jq '.files[] | "\(.path)\t+\(.additions) -\(.deletions)\t"'` - **Branch comparison** `git log <main|master>..<branch>` `git diff --stat <main|master>..<branch>` - **Ambiguous mention** (PR number, branch name): infer the right form and fetch without asking unless auth fails. ### Categorize files Assign each file to a category based on its path: - **Core Logic**: application source (e.g. src/auth/login.py, database/models.ts) - **Generated**: anything with `generated` in its path - **Testing**: test files - **Config / Dependencies**: package.json, docker-compose.yml, etc. - **Documentation**: READMEs, docs/ - **Noise**: lock-files, .svg, auto-generated migrations For each file, record: path, category, change type (Added / Modified / Deleted), and analytics likelihood (1–5). ## Step 2: Build the file summary map Read every single **Core Logic** file and create the file summary map. Only process and include **Core Logic** files.
Details
- Skill name
diff-intake- Repository
- amplitude/mcp-marketplace
- Path
plugins/amplitude/skills/diff-intake/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Diff Intake skill do?
Reads a PR or branch diff and produces a structured YAML change brief for downstream analytics instrumentation skills. Use this as the first step whenever a user shares a PR link, branch comparison, or raw diff and wants to understand what changed, what needs tracking, or how to instrument a feature. Trigger on phrases like "review this PR", "what changed in this branch", "help me instrument this diff", "check analytics coverage for this change", or any request to start the analytics review workflow.
How do I install the Diff Intake skill?
Claude Code plugin: /plugin marketplace add amplitude/mcp-marketplace. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Diff Intake popular?
It lives in amplitude/mcp-marketplace, which has 48 GitHub stars and 12 forks.
Related skills
Add Analytics Instrumentation
48amplitude/mcp-marketplace
End-to-end analytics instrumentation workflow for a PR, branch, file, directory, or feature. Reads the code, discovers what events should be tracked, and produces a concrete instrumentation plan — all in one shot. Use this skill whenever a user wants to add analytics to a PR, asks "instrument this PR", "add tracking to this branch", "what analytics does this file need", "instrument the checkout flow", "run the full instrumentation workflow", or any request that implies going from code changes to a tracking plan. Also trigger when the user gives you a PR link, branch name, file path, or feature
Analyze Account Health
48amplitude/mcp-marketplace
Summarizes B2B account health by analyzing usage patterns, engagement trends, risk signals, and expansion opportunities. Use for customer success reviews, renewal preparation, QBRs, or account prioritization.
Analyze AI Topics
48amplitude/mcp-marketplace
Analyzes what users ask AI agents about and how well each topic is served. Only use when the user has Amplitude Agent Analytics instrumented in their project. Use when the user asks "what are people asking the AI", "top AI topics", "where is the AI struggling", "AI coverage gaps", "what should we improve in our AI", or wants product insights from AI conversation patterns.
Distributed Mesh
45Azure-Samples/agent-skills-dotnet-demo
How to coordinate with squads on different machines using git as transport
Using Git Worktrees
43obra/clank
Create isolated git worktrees with smart directory selection and safety verification
Gh Auth Isolation
45Azure-Samples/agent-skills-dotnet-demo
Safely manage multiple GitHub identities (EMU + personal) in agent workflows
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.