--- title: "What Skene catches | Skene" description: "Five ways a release breaks tracking: removed, renamed, moved, changed field and conditional firing. Only the first leaves a gap you can see." url: https://www.skene.ai/product/features doc_version: "e4c10612d3cc" last_updated: 2026-08-29 --- Features # What Skene catches. A release can break tracking in five ways: the call is removed, renamed, moved, sending a different field, or firing for a different set of people. Code review catches the first one. The other four leave a call in place that still runs, so nothing looks wrong until a number does. [Start the free audit](https://www.skene.ai/signup) [See how it works](https://www.skene.ai/product/how-it-works) Free tier. No credit card. Events / skene-dashboard 3 unmapped | Event | Type | Status | | --- | --- | --- | | signup_completed | removed | missing | | account_created | renamed | unmapped | | plan_tier | changed field | field dropped | | upgrade_started | moved | fires earlier | | trial_ended | conditional firing | wider audience | | workspace_opened | unchanged | ok | The five failure modes ## The other four leave a call in place that still runs. Removed, renamed, moved, changed field, conditional firing. Only the first leaves a gap you can see. Visible ### Removed The call is gone. The chart goes flat and someone eventually asks why. [Start the free audit](https://www.skene.ai/signup) Renamed The call still runs Moved The call still runs Changed field The call still runs Conditional firing The call still runs Renamed `account_created · unmapped` The event still fires. Every funnel reading the old name reads nothing. ## A finding is an edit, not a mystery score. The check names the event, the file and why it failed, then posts a review you can apply in one click. - The review comments on the exact lines that changed - Where the fix is one line, the comment is a suggestion you commit from the pull request SkeneTechnologies/skene-dashboard #312 changes requested S skene-ai bot Skene Analytics Drift Review This pull request has 1 tracking issue (1 fires early). See inline comments. What breaks Warn: `upgrade_started` fires earlier at `billing.ts:31` src/billing/billing.ts 1 comment On every release ## Every release, checked. Skene Cloud reviews every pull request on the repository you link for removed or broken tracking, then posts findings on the PR. - Removing or breaking an event the collection plan needs gets changes requested - A table that is there with no sample behind it is reported and blocks nothing - The number that tells you a release worked stays trustworthy, because a broken merge gets caught first Skene / Before you ship On every release 1. Plan 2. Verify 3. Launch ready 4. Check A plan reaches launch ready only when the signals it needs already exist. [Know before you ship →](https://www.skene.ai/evaluator) Four surfaces, one engine ## In your coding agent, on your pull requests, in the cloud, or on your machine. Surfaces MCP server Cursor, Claude Code GitHub App Runs on every PR Cloud Keeps a record Command line MIT, no account GitHub App The release check above. Reviews every change on the repository you link, and requests changes when a pull request removes or breaks an event the collection plan needs. The check also fails when a table the plan needs is missing from your database. What this is not ## Not a replacement for your analytics. Skene does not store, model or visualise event data. Your code Where tracking calls live, and where releases break them. Skene Watches the code that records your events. Comments, never pushes. Your analytics PostHog, Mixpanel, Segment and the rest keep running. You do not move a dashboard. - **Your analytics and BI tools keep running** Skene watches the code that records your events, and the events keep going where they go today. You do not move a dashboard. - **Skene OSS and the free audit are two products** Skene OSS is the MIT-licensed command-line tool, public at [github.com/SkeneTechnologies/skene](https://github.com/SkeneTechnologies/skene). No Skene account, and you supply the model provider. - **A Skene OSS run creates neither an account nor a workspace** The free audit runs inside Skene Cloud, behind sign-in. - **Findings arrive as comments, never as changes** Skene comments on the change that broke tracking. It never pushes to your default branch. ## Start the free audit. Sign in, create a workspace, connect a source, and Skene returns one audit of what your product collects. [Start the free audit](https://www.skene.ai/signup) [See Skene OSS](https://www.skene.ai/community/open-source) ## Sitemap - [Markdown sitemap](https://www.skene.ai/sitemap.md): every page on this site, with its markdown counterpart. - [Index for language models](https://www.skene.ai/llms.txt): the same set as a link-dense index. - [Full corpus](https://www.skene.ai/llms-full.txt): reference content concatenated as plain text.