Skip to content

Developers

Skene reviews your pull requests for tracking that breaks.

A refactor can pass its tests and remove the event a growth experiment is measured by. Skene reviews your pull request and gives you a specific finding to act on before merge.

Team invitationsProposed refactor · review required
Journey requirementRecord when an invited teammate becomes active.teammate_activated
Engineer or coding agent · Proposed code change
  activateTeammate(invitation)− track("teammate_activated")  return success()
Skene · Review finding

Required tracking call removed.

This change removes the event required for the teammate activation milestone. The analytics tracking review flags it before merge.

Changes requested
You review the correction.

A finding does not merge a change. An engineer approves it first.

Human review

Product preview

From finding to correction

Each finding comes with a correction you review.

The review names the issue. The correction follows the kind of change you need.

Accept a small edit

For a supported inline edit, Skene supplies a GitHub suggestion. You inspect and commit it.

Prepare new tracking

Skene supplies implementation instructions naming the event and relevant code. Your coding agent prepares the change. Engineering reviews it.

Restore a removed call

Comment /skene fix to request a follow-up pull request restoring removed calls. It cannot add an event that never existed.

Run the review again after the correction. A later passing review dismisses Skene’s earlier change requests on that pull request.

Two review paths

Choose the check for the change.

Agent or CI

Compare against the baseline.

The deterministic check compares scanned tracking with planned requirements. A missing event in the scan is a code finding.

Explore the MCP server
GitHub pull request

Review the changed code.

The pull request review uses a model to assess the diff against tracking policy. You review its findings.

Read the reference

These checks can return different findings. Neither replaces your tests or establishes that runtime events are arriving.

Install the GitHub App on the repositories you choose.

You choose all repositories or a selected set when you install the app, then a workspace owner links the repository and enables reviews. Proposed changes arrive as pull requests.
Permissions requested by the Skene GitHub App
PermissionAccessPurpose
ContentsRead & writeRead source and context files; propose updates through pull requests.
Pull requestsRead & writeRead changes, post reviews and open fix pull requests.
IssuesRead & writeRespond to /skene fix comments.
MetadataReadList repositories accessible to the installation.

Skene OSS

Keep the journey in your repository.

Run uvx skene analyse-journey . with your chosen model provider, and it writes skene-context/journey.yaml with the source evidence for each step. Cloud adds the shared workspace and hosted reviews.

Add tracking checks to your pull requests.

Sign in and 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