GitHub Integration

Skene connects to GitHub through the Skene GitHub App. You install the app on your account or organization, choose which repositories it can see, and link one of them to your workspace. No personal access tokens to mint or rotate.

The linked repository is what makes the checks real. Skene uses it to:

• Scan your codebase for analytics events and tracking calls, which grounds the journey and gap analysis for your workspace.
• Sync skene-context/: Skene reads journey and engine files from the repo and writes updates back through pull requests, so the record of what your tracking means lives in your own repo.
• Review pull requests for broken or removed tracking, and open fix PRs on request (see PR reviews below).

Prerequisites

• A GitHub account with access to the repository you want to link. Installing the app on an organization may need an org owner's approval, depending on the org's settings.
• A Skene workspace where you are the owner. Members can add GitHub accounts, but only owners can link or unlink the workspace repository.

Connect a repository

You can connect during onboarding or any time later from Settings → GitHub in your workspace.

1. Install the GitHub App

Open the GitHub repository card and click Connect Git repository (onboarding), or click Continue with GitHub (settings). A popup opens GitHub's install screen, where GitHub asks you two things:

1. Where to install: your personal account or one of your organizations.
2. Which repositories: all repositories, or only the ones you select.

Selecting only the repositories you need is fine. You can change the selection later from GitHub, or via the Change permissions link in Skene's repository picker.

2. Pick the repository

Back in Skene, the repository picker lists everything the installation can access, most recently pushed first. If you've connected more than one GitHub account, pick the account first, then the repository, then confirm (Confirm repository in onboarding).

That's it. The tile flips to show the linked repository, and the connection is shared with your workspace: teammates use the same installation instead of each connecting their own.

One repository per workspace, several workspaces per repository

Each workspace links exactly one repository and branch. Choosing a different repository replaces the link (the app installation itself is untouched).

The reverse is allowed: the same repository can be linked to as many workspaces as you like, which is how one team runs staging, production, and demo workspaces off a single repo. Linking a repository another workspace already uses still succeeds, and Skene shows a warning naming the workspaces it is shared with. Every linked workspace then gets its own skene-context/ sync and its own PR review on each delivery, so a workspace you only created to try something out keeps doing that work on every push. Unlink the ones you no longer need.

What the app can access

The Skene GitHub App requests repository-level permissions, scoped to the repositories you selected at install time:

Skene never pushes directly to your default branch. Changes it proposes arrive as pull requests you review and merge yourself.

PR reviews

The PR reviews switch lives in Settings → GitHub. When it's on, Skene reviews every pull request on the linked repository and flags removed or broken tracking events. Owners only.

Here's the loop:

1. Someone (or something: this is built for codebases where agents write the code) opens a PR that renames a tracked event or deletes the call entirely.
2. Skene reads the diff, checks it against what your workspace knows about your tracking, and posts a review. A problem gets request changes with inline comments on the exact lines; a clean PR gets a pass.
3. Where the fix is a one-line edit, the inline comment is a GitHub suggestion you can commit from the PR. Where it isn't, the comment carries a Prompt to fix this block instead: a self-contained instruction you can paste straight into a coding agent, naming the file, the line, and the event to restore or add.
4. If a review flags tracking the PR removed, anyone on the repo can comment /skene fix. Skene reacts, then opens a follow-up PR onto the same branch that restores the missing tracking calls for you to review. /skene fix only restores what the PR deleted; it cannot add an event that never existed, so for missing tracking use the prompt block instead.

Once a later run passes, Skene dismisses the change requests it left earlier on that PR, so a fixed branch stops being blocked by a stale review.

If several workspaces link the same repository, each one with PR reviews enabled judges the diff and records its own result on its Pull requests page. Only one of them posts to GitHub: the workspace that linked the repository first, which is also the one that gates /skene fix. That keeps a single review on the PR no matter how many workspaces are watching.

Review activity also shows up in your workspace on the Pull requests page.

Managing the connection

From Settings → GitHub:

• Change repository: link a different repo from the same installation.
• Unlink repository: remove the repo link but keep the GitHub account connected.
• Add GitHub Account: install the app on another account or org (for example, personal and work).
• Change permissions: reopen GitHub's install screen to grant access to more repositories.
• Disconnect: remove the GitHub account connection from Skene.

To remove Skene's access entirely, uninstall the Skene GitHub App from GitHub (Settings → Applications on the account or org where you installed it). That revokes every permission at the source.

Troubleshooting

"No repositories found"

The installation exists but can't see any repositories. Click Change permissions and grant the app access to the repository you want (or switch from "selected repositories" to include it).

"Owner access required"

Linking and unlinking the workspace repository is owner-only. Ask the workspace owner to link the repo, or to make you an owner.

The repository picker shows the wrong account

If you've installed the app in more than one place, use the account dropdown above the repository list. Missing an account entirely? Use Add GitHub Account to install the app there.

Next steps

• Quickstart: the full first-run setup
• Supabase Integration: connect your database schema
• Logs: watch events and decisions in real time