add-analytics-instrumentation

What problem does it solve?

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 description and mentions analytics, events, or instrumentation. This is the main entry point for the analytics workflow — prefer it over calling the individual steps (diff-intake, discover-event-surfaces, instrument-events) separately.

Core Features & Use Cases

• End-to-end instrumentation workflow: reads code changes and outputs a concrete tracking plan.
• Supports PR, branch, file, or feature inputs; triggers when user mentions analytics.
• Orchestrates the instrumentation workflow across steps to produce actionable results.

Quick Start

Describe the code changes you want instrumented (a PR, a branch, or a file) and I will generate a full analytics instrumentation plan.