From amplitude
Analyzes PR or branch diffs to produce YAML change briefs categorizing files, summarizing core logic changes, user-facing updates, and interaction surfaces for analytics instrumentation.
npx claudepluginhub amplitude/mcp-marketplace --plugin amplitudeThis skill uses the workspace's default tool permissions.
Follow this skill step by step.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Builds scalable data pipelines, modern data warehouses, and real-time streaming architectures using Spark, dbt, Airflow, Kafka, and cloud platforms like Snowflake, BigQuery.
Builds production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. For data pipelines, workflow orchestration, and batch job scheduling.
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.
Fetch the list of changed files from the source, then categorize each one.
gh pr view <number-or-url>
gh pr view <pr-number> --json files --jq '.files[] | "\(.path)\t+\(.additions) -\(.deletions)\t"'git log <main|master>..<branch>
git diff --stat <main|master>..<branch>Assign each file to a category based on its path:
generated in its pathFor each file, record: path, category, change type (Added / Modified / Deleted), and analytics likelihood (1–5).
Read every single Core Logic file and create the file summary map. Only process and include Core Logic files.
gh pr view <number-or-url> --json baseRefOid,headRefOid
Using the response, get a detailed diff
git diff <baseRefOid>...<headRefOid> -- <file1> <file2> <file_n>git diff main..feature/foo -- <file1> <file2> <file_n>summary — 2-line summary of what changedstack — frontend, backend, or sharedWhile reading the diff and the changed files, also produce the higher-level signals that downstream event discovery needs:
user_facing_changes — a flat list of concrete behavior changes that matter
to a user, PM, or analyst. Each item should describe what a user can now do,
see, or experience differently. Omit purely internal refactors.surfaces.components — the UI components, routes, pages, handlers, or other
interaction surfaces directly involved in those user-facing changes. Prefer
likely instrumentation points over low-level helpers.For each surface, record:
name — component, route, page, hook, or surface namefile — repo-relative pathchange — added, modified, or deletedIf the change is backend-only or has no clear interactive surface, omit
surfaces.components rather than inventing one.
Infer the change type and analytics scope:
| Type | Analytics implication |
|---|---|
| feat | High — new surfaces likely need tracking |
| fix | Low–Medium — may affect existing event conditions |
| refactor | Low — tracking paths may move, regression risk |
| perf | Low — usually no tracking impact |
| revert | Medium — need to check what tracking was lost |
| style / docs / test / build / ci / chore | None — skip analytics analysis |
analytics_scope = highest implication present:
none — only no-impact typeslow — only perf/refactormedium — fixhigh — any feature or capability additionIf analytics_scope is none, emit the brief and note that downstream skills are not needed.
Output only the YAML block — no prose before or after. Follow the format exactly. List each file individually in file_summary_map (no globs).
change_brief:
classification:
primary: feat # dominant conventional commit type
types: [feat, fix] # all types detected
analytics_scope: high # none | low | medium | high
stack: frontend # frontend | backend | fullstack
summary: "One sentence describing the overall change"
user_facing_changes:
- "Users can now upload an avatar with drag-and-drop and preview it before saving."
surfaces:
components:
- name: "AvatarUpload"
file: "src/components/AvatarUpload.tsx"
change: modified
file_summary_map: # each entry includes a layer field
- file: "src/components/AvatarUpload.tsx"
summary: "New component for avatar upload with drag-and-drop and preview"
layer: frontend # frontend | backend | shared
- file: "src/api/upload.ts"
summary: "Upload endpoint handler, validates file type and persists to S3"
layer: backend