skills.rest
amplitude
amplitudeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

diff-intake

Reads a PR or branch diff and generates a structured YAML change brief.

28|Updated Dec 5, 2025
Search Tags:#workflow#analytics#yaml#instrumentation#diff#pr#change-brief
One-click install
npx skills add https://github.com/amplitude/wizard --skill diff-intake
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diff-intake
Source: https://github.com/amplitude/wizard/tree/main/skills/instrumentation/diff-intake
Command: npx skills add https://github.com/amplitude/wizard --skill diff-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reads a PR or branch diff and produces a compact 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.

Core Features & Use Cases

  • Generates a structured YAML brief summarizing file changes and categorization for analytics instrumentation pipelines.
  • Supports PR view, branch diffs, and raw diffs as input sources; outputs ready-to-consume data for downstream skills such as discover-event-surfaces and instrument-events.
  • Use case: when a team asks which analytics events to instrument after a PR, run this intaker to produce a consistent YAML brief.

Quick Start

Run the intake against a PR URL, branch comparison, or diff to generate a YAML brief for instrumentation.

Frequently Asked Questions about diff-intake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an analytics change brief from a PR diff?▼

You can generate an analytics change brief by providing a PR link, branch comparison, or raw diff, which produces a structured YAML summary of file changes for downstream instrumentation pipelines.

What is the best way to summarize branch changes for analytics instrumentation?▼

Summarizing branch changes for analytics instrumentation involves reading the diff and categorizing file modifications into a concise YAML change brief, ready for downstream skills to identify what needs tracking.

Can I use a raw diff to determine what analytics events need tracking?▼

Yes, you can use a raw diff to determine what needs tracking by converting the diff into a structured YAML change brief that categorizes file changes for downstream analytics instrumentation workflows.

Does the analytics change brief output support direct integration with downstream instrumentation workflows?▼

The YAML change brief output supports direct integration with downstream analytics instrumentation workflows by providing categorized file change data ready for consumption by discover-event-surfaces and instrument-events skills.

When do I need to create a YAML change brief from a pull request?▼

You need to create a YAML change brief from a pull request when a team asks which analytics events to instrument after a change, requiring a consistent summary of file modifications for the instrumentation pipeline.

Related Skills

Explore More Data & Analytics Skills→
eglenn-deveglenn-dev
1

pr-summary

Generates a structured pull-request summary from git diff, file list, commit history.

Community
Basic
majiayu000majiayu000
258

product-analytics

Define event tracking schemas and validate analytics data modeling.

Community
Advanced
Dawn-TechnologyDawn-Technology
9

review-pr

Generate evidence-based review findings for GitHub Pull Requests or GitLab Merge Requests.

Official
Advanced
storyblokstoryblok
60

review-and-qa

Analyze code changes to generate a structured QA review plan.

Official
Basic