Skip to main content
This guide installs Sigilix on a single repository and walks you through your first review.
Sigilix is in private beta — there’s no public self-serve signup or paid plan yet. Join our private beta to get your account provisioned.

​
Prerequisites

  • A GitHub account with admin permissions on at least one repository
  • A Sigilix beta account (join the private beta)
  • A few minutes

​
1. Install the GitHub App

1

Join the private beta

Go to app.sigilix.ai and request access. Once your account is provisioned, sign in to continue.
2

Sign in with GitHub

Click Sign in with GitHub and authorize the Sigilix OAuth app. This is read-only at this stage — no code is fetched yet.
3

Install the GitHub App

Click Install Sigilix on a repository. GitHub’s standard App-installation flow opens. Choose:
  • The account or org that owns the repository
  • Which repositories to install on (start with one)
Required permissions:
  • Pull requests · Read & write (to post reviews and inline comments)
  • Contents · Read (to fetch the diff)
  • Metadata · Read (default)
  • Issues · Read & write (to handle @sigilix mentions)
Click Install. You’re returned to your Sigilix dashboard.

​
2. Trigger your first review

Open any pull request on the installed repository — or push a new commit to an existing PR. Sigilix listens for the pull_request.opened and pull_request.synchronize webhook events.
Don’t have a PR handy? Open a tiny one — change a single string in the README — to see Sigilix in action without spending much of your review budget.
Within a minute or two, you’ll see a new review on the PR from sigilix[bot]. The review includes:
  • A summary from Harmonia (the synthesizer): what was reviewed, how many findings survived dedup, and the verdict
  • Inline findings (if any) anchored to specific lines, tagged by specialist (Metis, Argus, Iris, Eunomia)
  • Severity badges: Critical / Warning / Info
  • A proof-tier pill on each finding (VERIFIED / GROUNDED / MODEL) — see the believability pipeline

​
3. Resolve findings

If Sigilix flagged real issues, fix them and push again. Sigilix re-reviews on every push (pull_request.synchronize) and updates the verdict — if all blocking findings are resolved, the next review approves. If a finding is a false positive or out of scope, reply to it. You can dismiss it, or teach Sigilix a rule so it stops happening: reply @sigilix remember <the rule> and it will apply — and attribute — that rule in later reviews. See Conversational Learnings.

​
4. Configure (optional)

If you need to tune behavior — ignore generated files, add per-role guidance, define deterministic regex rules — drop a sigilix.json (or sigilix.yaml) at the root of your repo. Sigilix reads JSON and YAML with the same schema. See Configuration for the full schema.

​
What’s next

The Believability Pipeline

The five gates a finding clears before it can post — and how to read the proof-tier pills.

GitHub Integration

Branch protection, required checks, multi-repo install, deeper GitHub integration.