It reads your pull request before your reviewer does.
Before you find out the hard way. It runs on every pull request opened, updated, or reopened: 3 trigger events, one review each time, not a sampled check.
The app never pushes to your default branch. Every change arrives as a pull request you review.
company_profile_saved missing at CompanyProfileStep.tsx:89GitHub App
Part of your developer workflows.
Database
Your product data stays in your own database.
Skene OSS
Run the OSS in your local environment.
The fix pins to a span. The prompt pastes into your agent.
An agent deletes a tracking call while refactoring. The review catches it before merge.
The fix pins to a single contiguous span.
When it does, the comment carries a suggestion you commit in one click. When it doesn't, it carries a prompt for your coding agent instead.
- Inline comments on the exact line that broke it
- A prompt block you can paste into a coding agent
company_profile_saved on the payload and version the rename.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
- Step 1
- Sign in
- Step 2
- Install the GitHub App
- Step 3
- Turn on PR reviews
The open-source half, on your machine.
Skene OSS is the MIT-licensed CLI and terminal UI at github.com/SkeneTechnologies/skene. It reads your repository, writes the customer journey it finds to skene-context/journey.yaml, and keeps a copy of nothing. You point it at your own model provider, and it needs no Skene account.
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
Already committed to your own repository.
The pull request review is the Cloud half
That is what would go.
Your product data stays in your own database
Uninstalling the GitHub App revokes every permission at the source.