See the tracking a pull request changes.
Skene checks tracking when a pull request is opened, reopened or synchronized. A removed tracking call gets an inline comment, before you merge the change.
Suggestions stay on the pull request for your team to review. The app never pushes to your default branch.
skene-ai[bot]
Changes requested
Missing tracking
This PR has 1 tracking issue (1 missing). See inline comments.
Medium
[event redacted] missing at [file redacted]:89
A finding you can act on. A later review you can compare.
In Skene’s own pull request, the review found a missing event. After the fix, a later review passed.
The review names the missing event.
The comment identifies the location and describes where the event belongs. The follow-up records what happened after the change.
- A source location and a suggested fix
- The initial finding and the later review, in order
skene-ai[bot]
Changes requested
Missing tracking
This PR has 1 tracking issue (1 missing). See inline comments.
Medium
[event redacted] missing at [file redacted]:89
Suggested fix
Skene Analytics Drift Review
After [save operation] succeeds and before [next step], emit the codebase's client analytics event for [event redacted], including the selected [properties redacted].
Later review
No tracking issues detected.
Skene analytics drift check passed. No tracking issues detected.
Earlier request dismissed
Tracking issue fixed; superseded by later Skene pass review.
Three steps, not a package install.
Sign in, install the GitHub App on a repository, turn on pull request reviews.
- Owner-only toggle
- If other workspaces watch the same repo, only the first to link it posts to GitHub
- 01Sign in
- 02Install GitHub App
- 03Enable reviews
A separate product, on your machine.
Skene OSS is the MIT-licensed CLI and terminal UI at github.com/SkeneTechnologies/skene. A local run reads your repository and writes the customer journey it finds to skene-context/journey.yaml. It needs no Skene account and uses the model provider you configure. Publishing is separate and happens only when you explicitly request it with a linked provider.
What you keep if we go away.
Skene OSS is MIT-licensed and runs with no Skene account and no service of ours behind it.
If Skene Cloud stopped tomorrow, the tool still runs
Skene OSS is public on GitHub and runs against a model provider you supply.
You keep the journey file and the tool that writes it
The CLI writes skene-context/journey.yaml in your working tree. You decide whether to commit it.
The pull request review is the Cloud product
That is what would go.
Your product data stays in your own database
Uninstalling the GitHub App revokes that app installation. Database, API and model-provider credentials remain separate.