discover-analytics-patterns

Identify analytics SDK call patterns and generate a structured pattern report from your codebase.

28|Updated Dec 5, 2025
One-click install
npx skills add https://github.com/amplitude/wizard --skill discover-analytics-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discover-analytics-patterns
Source: https://github.com/amplitude/wizard/tree/main/skills/instrumentation/discover-analytics-patterns
Command: npx skills add https://github.com/amplitude/wizard --skill discover-analytics-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers understand how analytics calls are implemented in a codebase by identifying the concrete SDK call patterns, wrapping utilities, and import conventions, enabling consistent instrumentation and easier onboarding for new tracking work.

Core Features & Use Cases

  • Discover representative non-system event patterns and wrappers by scanning code for analytics SDK calls.
  • Group and deduplicate patterns by shared library, function, and argument structure, with a map of file paths where each pattern appears.
  • Infer event and property naming conventions from real usage and present guidance for consistent instrumentation across future changes.

Quick Start

Run the discover-analytics-patterns skill to scan your repository and generate a pattern report for analytics instrumentation.

Frequently Asked Questions about discover-analytics-patterns

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

FAQPage Schema
How do I find analytics tracking patterns across my codebase?

You can discover how analytics calls are implemented by scanning your repository to locate SDK calls, grouping them by shared library and argument structure, and mapping file paths where each pattern appears.

How do I identify analytics instrumentation wrappers and naming conventions in a repository?

Identifying analytics instrumentation wrappers involves scanning code for SDK calls, extracting import conventions and wrapping utilities, and inferring event and property naming conventions from real usage to guide consistent tracking.

Can I deduplicate analytics event tracking calls by library and method?

Yes, you can deduplicate analytics event tracking calls by grouping them based on shared library, function, and argument structure, producing a structured pattern report that maps real call sites.

Does this approach work for extracting SDK usage patterns without system events?

Yes, this approach works for extracting SDK usage patterns by specifically locating representative non-system event patterns and filtering out system events to focus on actual analytics tracking calls.

What is the best way to standardize analytics tracking implementation across a codebase?

The best way to standardize analytics tracking implementation is to map existing SDK call patterns, deduplicate them by function and argument structure, and infer naming conventions from real usage to guide future instrumentation.