Skene
Product
Pricing
Docs
Blog
Events
About
Log InStart free
ProductPricingDocsBlogEventsAbout
Log InStart free
Skene subpage background texture
  1. Home
  2. /
  3. Product
  4. /
  5. Architecture
ARCHITECTURE

Parser, indexer, comparator, reporter.

Four components. No background daemons, no agents talking to agents, no LLM in the hot path. Static analysis with a baseline and a semantic diff.

  • How it works
  • Features
  • Architecture
  • Security
  • Integrations
  • Pricing
  • Parser

    Static analysis, no runtime. Skene parses the repository into an AST and walks every call site. Nothing executes. Nothing reaches your customers' browsers or your servers. The same approach a TypeScript compiler or an ESLint plugin uses to read your code.

  • Indexer

    For every place your code writes an event, Skene records the target table, the columns the payload sets, the file path, the line number, and the control-flow context. The output is a structured map. The map is your baseline.

  • Comparator

    On a PR, Skene rebuilds the map for the new state of the repo and diffs it against the baseline. The diff is semantic: it ignores formatting and reordering and surfaces only changes that affect what your code writes into your Supabase tables.

  • Reporter

    Findings get serialized in three shapes: a markdown PR comment, an MCP response back to the coding agent, and a JSON payload for the cloud API. One engine, three output formats.

PRINCIPLES

Three things to know

  • Static, not runtime

    Skene does not instrument your app, intercept network calls, or sit in your data pipeline. It reads the same source files your linter does.

  • Open core

    The parser, indexer, and comparator are open source on GitHub. The cloud-managed surfaces (hosted API, dashboard) are paid. Audit what runs against your code.

  • Workspace isolation

    When you run Skene on the cloud API, your indexed manifest lives in an isolated workspace tied to your repository. Manifests are not pooled, not used to train anything, not shared across customers.

Start freeRead the source
Pixelated Skene CTA background

Patch the code tomorrow. The data from this week is already gone.

A renamed event passes every test, ships green, and sits broken for weeks before anyone notices. Skene runs as a GitHub Action on every pull request, reads your Supabase schema read-only, and comments the moment a write breaks, while your data is still recoverable. Usage-based on tokens, with $5 of free cloud credit to start. A PR that touches none of your tracking costs nothing.

Start free
Skene

Product

How it worksFeaturesSupabaseArchitectureIntegrationsSecurityPricing

Resources

DocumentationGlossaryPlaybooksBlog

Company

AboutOpen sourceContactPrivacyTerms
© 2026 Skene. All rights reserved.
Privacy PolicyTerms of Service
Skene