Skene and coding agents
The feature can work while its tracking is missing.
A coding agent can ship a working feature and drop the event a growth experiment is measured by, such as teammate_activated. Skene checks each change against the experiment’s tracking plan before you merge.
Prepare the change.
Implement the refactor and run the project’s tests.
− track("teammate_activated")Check the requirement.
Compare tracking evidence with the planned milestone.
teammate_activatedReview the correction.
Inspect the finding and proposed change. Decide what to merge.
Product preview
Make the requirement explicit.
| Evidence | Finding | Meaning |
|---|---|---|
| Application tests | Pass | Tested application behavior works. |
| Journey requirement | teammate_activated | Required for the activation milestone. |
| Changed code | Required call removed | Tracking correction needs review. |
| Runtime evidence | Not evaluated by this code comparison | Check the connected event source separately. |
The hosted MCP check compares the agent’s supplied scan with the journey baseline. Authorized tools can edit that baseline, so control its write access too.
Match the correction to the gap.
Restore the deleted call.
The GitHub review can supply a suggestion or fix prompt. For removed calls, /skene fix requests a restoration pull request for engineer review.
Prepare the missing event.
Use the supplied implementation prompt or supported suggestion. The restoration command cannot create an event that the pull request did not delete.
Two checks answer different questions.
Add tracking checks to the next review.
Install the GitHub App on a repository. Your first experiment is free with no card, and pull request reviews come with every plan, Free included.
Measure your first experiment free