Quick Start
Get Xavier running and review your first diff in three steps.
Install
curl -fsSL https://raw.githubusercontent.com/atilafassina/xavier/main/install.sh | shThe installer:
- Scaffolds your vault at
~/.xavier/ - Detects your active AI runtime (Claude Code, etc.)
- Wires the appropriate execution adapter
- Kicks off the interactive setup
Setup
If the installer didn't trigger setup automatically, run:
/xavier setupXavier interviews you to personalize your experience:
- Your name — how Xavier addresses you
- Your teams — links to team-level conventions
- Workflow preferences — how you like to work
- Review priorities — "what kind of reviews matter most to you?"
- Git strategy — how Xavier commits to the vault (batch-commit by default)
- Export vault path — optional path to your personal Obsidian vault
Setup also:
- Creates a private GitHub repo for your vault (default name:
xavier-ai) - Installs three default reviewer personas: correctness, security, and performance
- Detects existing global skills and coexists without conflict
Your first review
Navigate to any repo with uncommitted changes and run:
/xavier reviewHere's what happens behind the scenes:
- Xavier detects your diff
- Three reviewer agents spawn in parallel — each with a distinct persona
- As each reviewer finishes, findings are aggregated incrementally
- You get a synthesized verdict: approve, request changes, or rethink
The review is stored as a note in your vault. Next time you review the same module, Xavier has context from this review.
Example: reviewing a PR
Say you're working on an auth module and you've got a branch ready:
git diff main..HEADRun /xavier review. The correctness reviewer catches a missing null check, the security reviewer flags a token stored in localStorage, and the performance reviewer notes an unnecessary re-render. You get all three perspectives in one pass, deduplicated and categorized.
What's next
- Code Review — understand personas, panel mode, and how reviews get smarter over time
- Dependency Management — add best-practice skills for your key packages
- How It Works — the Shark pattern and Zettelkasten vault explained
Last updated: 4/8/26, 10:45 PM
Edit this page on GitHub