segment-cdp
Client-side tracking with Analytics.js. Include track, identify, page, and group calls. Anonymous ID persists until identify merges with user.
Click Get this skill. Grab the .md file, one click, no account needed.
Add it to Claude. Drop it into ~/.claude/skills/. Claude picks it up the next time you open a session.
Ask normally. Type your question. The skill triggers on the right keywords — you don't have to remember anything.
Generate conventional commit messages by analyzing staged changes
Find and delete merged/stale local and remote branches
Safely undo the last git operation (commit, merge, rebase, etc.)
Generate CHANGELOG.md from git history using conventional commits
Analyze and suggest resolutions for merge conflicts
Automate git bisect to find the commit that introduced a bug
## Patterns ### Analytics.js Browser Integration Client-side tracking with Analytics.js. Include track, identify, page, and group calls. Anonymous ID persists until identify merges with user. ### Server-Side Tracking with Node.js High-performance server-side tracking using @segment/analytics-node. Non-blocking with internal batching. Essential for backend events, webhooks, and sensitive data. ### Tracking Plan Design Design event schemas using Object + Action naming convention. Define required properties, types, and validation rules. Connect to Protocols for enforcement. ## Anti-Patterns ### ❌ Dynamic Event Names ### ❌ Tracking Properties as Events ### ❌ Missing Identify Before Track ## ⚠️ Sharp Edges | Issue | Severity | Solution | |-------|----------|----------| | Issue | medium | See docs | | Issue | high | See docs | | Issue | medium | See docs | | Issue | high | See docs | | Issue | low | See docs | | Issue | medium | See docs | | Issue | medium | See docs | | Issue | high | See docs | ## When to Use This skill is applicable to execute the workflow or actions described in the overview.