diff-intake skill (Amplitude): turn a PR or branch diff into an analytics change brief

Amplitude's own skill that reads a PR or branch diff and outputs a YAML change brief for the analytics instrumentation workflow.

Installs: 48.8K; on skills.sh
Stars: 46; on GitHub
Updated: Oct 2026; last repo commit

diff-intake makes your coding agent read a pull request or branch diff and write a short YAML change brief. The brief sorts changed files, summarizes the core logic, lists user-facing changes and touched UI surfaces, and rates how much the change needs analytics.

It is step 1 of Amplitude's instrumentation workflow. The brief feeds discover-event-surfaces and instrument-events. It uses the gh and git commands, so a PR link needs a working gh login.

Good for

Developers who want to know what a PR changes and whether it needs tracking
Teams starting Amplitude's instrumentation workflow from a diff

Install diff-intake

Claude Code

Copy this prompt.

Install the diff-intake skill in Claude Code. Run this command:

claude plugin install amplitude

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

diff-intake only needs gh and git, so the skills CLI route installs just this skill. The downstream skills that use its brief (discover-event-surfaces, instrument-events) are optional hand-offs and need the Amplitude MCP server. The plugin route installs all 36 Amplitude skills and registers that MCP server.

From the project README. Source.

What's in the skill

When it loads

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.

Sections in SKILL.md

Step 1: Gather changed files and categorize
Fetching changes
Categorize files
Step 2: Build the file summary map
Fetching detailed diffs
For each file, record
Also derive user-facing changes and touched surfaces
Step 3: Classify the overall change
Step 4: Emit the YAML brief

Key facts

Author: Amplitude (vendor's own repo; the README calls it the official Amplitude plugin)
License: MIT (LICENSE file, README and plugin manifests agree)
Installs on skills.sh: 48,771 as of 2026-11-02
GitHub stars: 46 for the whole mcp-marketplace repo, 2026-11-02
What is inside: 1 file: SKILL.md. It bundles no scripts.
Last change to this skill: 2026-03-26
Part of: The amplitude plugin (version 1.7.0 in the marketplace file) in the amplitude marketplace
Works in: Claude Code, Cursor, Codex, Gemini CLI and Claude, per the README

What it includes

Lists changed files and sorts them
Uses gh pr view for a PR or git log and git diff --stat for a branch. Files are labeled Core Logic, Generated, Testing, Config, Documentation or Noise, with change type and an analytics likelihood score of 1 to 5.
Try: “Review this PR for analytics coverage: https://github.com/org/repo/pull/42”
Runs code · Step 1: gather and categorize files
Reads each core-logic file's diff
Gets the base and head commits with gh, runs git diff for the core files, and records a two-line summary and a layer (frontend, backend or shared) for each.
Runs code · Step 2: file summary map
Names behavior changes and the components involved
Lists what a user can now do, and the components, routes or handlers involved. Backend-only changes omit surfaces.
Read · User-facing changes and surfaces
Sets the analytics scope
feat gives high, fix gives medium, refactor and perf give low, and revert gives medium. Docs, test, build, ci and chore give none.
Read · Step 3: classify the change
Outputs only the change_brief block
Machine-readable, with no prose around it, listing each file individually. If the scope is none, downstream skills are not needed.
Read · Step 4: emit the YAML brief

From the official docs

Permissions

Low risk

The agent runs gh and git commands to fetch a PR or branch diff, and reads your source files. The wider workflow it feeds can write events to Amplitude after you confirm.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

A private PR needs your gh login
SKILL.md says to infer the PR or branch and fetch without asking unless auth fails. Make sure gh is logged in to the account you mean to use. github.com
The plugin route installs 36 skills and the Amplitude MCP config
The git tree holds 36 skill folders under plugins/amplitude/skills, while the README lists 27. The plugin also bundles .mcp.json for https://mcp.amplitude.com/mcp, which you sign in to. The README lists skills that create charts and dashboards. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details

Talks to	GitHub, through the gh CLI, when you give a PR link
Sign-in and keys	PR access uses your existing gh login.
Scopes	Runs gh pr view (including --json files, baseRefOid and headRefOid) and git log, git diff --stat and git diff Reads the changed core-logic files

Questions

What does diff-intake do?

It reads a PR or branch diff and outputs a YAML change brief: file categories, summaries of core logic, user-facing changes, touched surfaces and an analytics scope. Other Amplitude skills use the brief.

How do I install diff-intake?

Use the install box at the top of this page. diff-intake only needs gh and git, so the skills CLI route installs just this skill. The skills that use its brief are optional hand-offs. The plugin route installs all 36 Amplitude skills.

Do I need an Amplitude account?

diff-intake itself only reads a diff with gh and git. The skills that use its brief, discover-event-surfaces and instrument-events, read from and can write to Amplitude, so the README lists an Amplitude account as a requirement.

Is diff-intake safe?

It runs gh and git commands and reads your source. The wider workflow it feeds can write events to Amplitude after you confirm, so read the confirmation lists there.

diff-intake or add-analytics-instrumentation?

add-analytics-instrumentation is the main entry point and runs diff-intake for you. Use diff-intake alone when you only want the change brief.

Is this the official Amplitude skill?

Yes. It is in Amplitude's own mcp-marketplace repo, which the README calls the official Amplitude plugin.

Does it work in the Claude app, Codex or Cursor?

The README names Claude Code, Cursor, Codex, Gemini CLI and Claude, and gives install steps for the first four. The skill runs gh and git against your repo, so there is no Claude app upload option here.

Information

updated Nov 2, 2026

Repository: amplitude/mcp-marketplace
Folder: plugins/amplitude/skills/diff-intake

amplitude/mcp-marketplace skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 5

README.md · github.com
marketplace.json · github.com
.mcp.json · github.com
plugin.json · github.com
SKILL.md · github.com