Quickstart
This guide installs Sigilix on a single repository and walks you through your first review.
Sigilix is live and self-serve. Start on the Free plan or start a 14-day Pro trial — no waitlist. See pricing for all plans.
Prerequisites
- A GitHub account with admin permissions on at least one repository
- A Sigilix account (sign up free)
- A few minutes
1. Install the GitHub App
Create your account
Go to app.sigilix.ai and sign up — start free, or begin a 14-day Pro trial. Then sign in to continue.
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.
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
@sigilixmentions)
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 the synthesizer: what was reviewed, how many findings survived dedup, and the verdict
- Inline findings (if any) anchored to specific lines, tagged by specialist (logic, security, performance, tests)
- Severity badges: Critical / Warning / Info
- A proof-tier pill on each finding (VERIFIED / REPRODUCED / 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.