add-analytics-instrumentation

Analytics tracking plans are generated by reading source code changes from a pull request, discovering relevant events, and orchestrating the workflow to output a concrete tracking plan. You simply describe the PR or provide a link to automate the end-to-end instrumentation.

Automating event instrumentation for a branch involves reading the code changes, identifying relevant event surfaces, and producing a concrete tracking plan. You can trigger this workflow by requesting tracking for a specific branch name or feature description.

Yes, you can instrument analytics for a single file. The workflow supports file-by-file instrumentation, reading the specified source code to discover what events should be tracked and generating a concrete tracking plan for that specific file.

Yes, the instrumentation workflow handles feature-level inputs. When you describe a feature or provide a file path alongside an analytics request, it reads the code changes and orchestrates the steps to deliver an actionable tracking plan.

You should use an end-to-end instrumentation workflow whenever you need to go from code changes to a tracking plan in one shot. It orchestrates the diff-intake, event discovery, and instrumentation steps automatically, making it preferable over calling the individual steps separately.