This is the main entry point for the instrumentation workflow in the Amplitude plugin. It first determines whether you provide a PR, branch, file directory, or feature description: PRs and branches are passed to diff-intake to generate change summaries, files are read directly and scanned for existing track, logEvent, and similar calls, while feature descriptions trigger searches through git commit history and code to locate relevant files. It then sequentially calls discover-event-surfaces to list candidate events and instrument-events to generate a JSON tracking plan, specifying which file and function each key event belongs to and which properties to send, finally asking if you want to adjust the plan or begin implementation.
Why it matters It directly derives the events to instrument, their code locations, and properties from code changes, while adhering to existing instrumentation patterns in the repository; it presents the plan for your review before modifying any code.
Security Audit: Not Audited
- Not yet scanned
Rationale
- skills.sh 24 hours installed 1521 (indicates attention only); 5 other skills from the same repository are ranked, and the repository README states it is an official Amplitude plugin under the MIT license
- SKILL.md has been read from the repository: it only reads code and git history, outputs a plan, and contains no steps for downloading or executing external scripts; if any step fails, it stops and does not proceed with incomplete data
Usage
- Run claude plugin install amplitude in Claude Code and follow the prompts to log in, then say "instrument this PR" or "add instrumentation to the checkout flow," and confirm each event listed by the plugin
Risks
- Has not yet undergone automated desktop auditing, and the website does not display installation commands
- Must be installed alongside diff-intake, discover-event-surfaces, and instrument-events from the same plugin to complete the entire workflow; the plugin requires an Amplitude account with API permissions