Diff intake: PR-to-analytics change brief
Read a PR or branch diff and emit a structured YAML change brief for downstream analytics instrumentation
- What
- Read a PR or branch diff and emit a structured YAML change brief for downstream analytics instrumentation
- Cost
- Free
- Needs
- the gh CLI (authenticated), git, a repo with the PR/branch/diff to analyze; pair with the companion skills discover-event-surfaces and instrument-events for the full workflow
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the first step of Amplitude's analytics instrumentation workflow: read a PR, branch comparison or raw diff, categorize every changed file, map the user-facing behavior changes and interaction surfaces, then emit a compact machine-readable YAML change brief (classification, summary, surfaces, file summary map) for downstream event discovery and instrumentation. By @amplitude, listed here with credit to its creator. Honest caveats: this is step 1 of a 3-skill chain — the brief is meant to be consumed by the companion skills discover-event-surfaces and instrument-events, not used alone; it requires the `gh` CLI and a git repo with the diff source. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Curated by Skill Harbor — the first step of Amplitude's analytics instrumentation workflow: read a PR, branch comparison or raw diff, categorize every changed file, map the user-facing behavior changes and interaction surfaces, then emit a compact machine-readable YAML change brief (classification, summary, surfaces, file summary map) for downstream event discovery and instrumentation.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit e61691fStep 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: the gh CLI (authenticated), git, a repo with the PR/branch/diff to analyze; pair with the companion skills discover-event-surfaces and instrument-events for the full workflow Install "Diff intake: PR-to-analytics change brief" for me. Give my agent the diff-intake contract from Amplitude's marketplace: fetch a PR or branch diff, categorize each changed file, read the Core Logic files, derive user-facing changes and interaction surfaces, classify the change type and analytics scope, then emit a compact machine-readable YAML change brief — output only the YAML block, no prose Repository: https://raw.githubusercontent.com/amplitude/mcp-marketplace/e61691f81196cfd9f4314a347f6d2b1c6106f780/plugins/amplitude/skills/diff-intake/SKILL.md Pinned version: install the code at commit e61691f81196cfd9f4314a347f6d2b1c6106f780 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "amplitude-mcp-marketplace-diff-intake". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. make sure the gh CLI is authenticated and fetch the companion skills for the full analytics workflow). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- e61691f · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.