Your coding agent, with an independent tracking check.
A feature can work with a tracking call missing. Skene compares the code with your planned events before the pull request.
No card needed.
4 finding classes checked against your planned baseline, deterministically, every run.
A missing event in Skene’s own code.
The GitHub App reviews the diff. MCP compares discovered events with your saved baseline. These checks can disagree.
Compares the code with a saved journey baseline.
The check compares scanned events with the workspace baseline, preferring the latest journey.yaml snapshot.
Required, but not found
Removed or weakened
A second check that can catch what the first one missed.
Skene Cloud reviews every pull request for removed or broken tracking. It shares no code with the MCP check.
- Too large for a one-click suggestion: a “Prompt to fix this” block
/skene fixrestores removed tracking calls, never adds an event that was never there
When a removed event needs restoring
/skene fix
Comment on the pull request. Skene can propose a restoration for a removed tracking call; your team reviews the change.
A command reference. The missing-event review above required a new event, so it did not use this fix path.
No card needed.
Before you connect it.
Is this just another gate my agent has to get past?
What if I already run other checks in CI?
How long does setup take?
What does the GitHub App actually have access to?
Run the check on your repository.
Skene OSS is the MIT-licensed CLI at github.com/SkeneTechnologies/skene. uvx skene analyse-journey . reads the repository and writes the journey to skene-context/journey.yaml. You point it at your own model provider.
