← ClaudeAtlas

rudder-tracking-reviewlisted

Checks RudderStack tracking changes against the live pipeline. Use when making or reviewing a code change to RudderStack tracking: an event name, an event property, a track, identify or page call, the SDK version or a wrapper. Always use it before you report such a change as done.
rudderlabs/rudder-agent-skills · ★ 19 · AI & Automation · score 77
Install: claude install-skill rudderlabs/rudder-agent-skills
# Tracking Review The code does not show what the pipeline expects from it. RudderStack knows the tracking plan, the events that the source receives today, the transformations, and the connected destinations. This skill has two parts: what to look for in a code change that touches analytics calls, and how to ask RudderStack about it. Use it when you review a change. Use it too when you edit such code yourself: check your edit before you report the task as done. It adds to your normal code review. ## When to use this skill | Situation | Use this skill? | |---|---| | A task makes you add, change, rename or remove `track`, `identify`, `page`, `screen`, `group` or `alias` calls | Yes, before you report the task as done | | "Will this change break our tracking?" | Yes | | A change bumps the RudderStack SDK version, or changes a wrapper around the SDK | Yes | | Review tracking plan or data catalog YAML | No. Use `rudder-tracking-plans` or `rudder-data-catalog` | | Review transformation code | No. Use `rudder-transformations` | | Events fail at a destination in production | No. Use `rudder-destination-debugging` | | AI events (`ai_*`, `mcp_*`) | No. Use `rudder-ai-events-verify` | ## When you made the change yourself A task that renames an event, adds a property or changes a call looks done when the code and the tests pass. The pipeline can still drop the event. Before you report the task as done: 1. Find the source that receives the events of the app. "How RudderStack helps"