xavier

Category: Tools & Productivity | Uploader: atilafassina | Downloads: 0 | Version: v1.0（Latest）

AI Agent Orchestrator & Knowledge System. Use when user says "/xavier setup", "/xavier review", "/xavier grill", "/xavier add-dep", "/xavier remove-dep", "/xavier deps-update", "/xavier uninstall", or any "/xavier" command.

Changelog: Source: GitHub https://github.com/atilafassina/xavier

Directory Structure

Current level: tree/main/xavier/

📁 deps/
- 📁 multi-model-dispatch/
  - 📄 dispatch.sh 2.7 KB
  - 📄 parse.sh 9.3 KB
  - 📄 SKILL.md 4.2 KB
📁 references/
- 📁 adapters/
  - 📁 claude-code/
    
    📄 adapter.md 2.7 KB
  - 📁 cursor/
    
    📄 adapter.md 3.2 KB
- 📁 formats/
  - 📄 zettelkasten.md 2.5 KB
- 📁 patterns/
  - 📄 backpressure-detection.md 929 B
  - 📄 debate.md 6.9 KB
  - 📄 destructive-ops.md 1.5 KB
  - 📄 monorepo-detection.md 1.1 KB
  - 📄 shark.md 3.0 KB
  - 📄 skill-delegation.md 1.6 KB
- 📁 personas/
  - 📄 correctness.md 1.6 KB
  - 📄 performance.md 1.9 KB
  - 📄 security.md 1.8 KB
📁 skills/
- 📁 add-dep/
  - 📄 SKILL.md 2.3 KB
- 📁 babysit/
  - 📄 SKILL.md 6.3 KB
- 📁 bug/
  - 📄 SKILL.md 1.8 KB
- 📁 deps-update/
  - 📄 SKILL.md 1.2 KB
- 📁 export/
  - 📄 SKILL.md 2.8 KB
- 📁 feedback/
  - 📄 SKILL.md 2.4 KB
- 📁 grill/
  - 📄 SKILL.md 3.4 KB
- 📁 learn/
  - 📄 SKILL.md 11.1 KB
- 📁 loop/
  - 📄 SKILL.md 4.5 KB
- 📁 prd/
  - 📄 SKILL.md 3.0 KB
- 📁 remove-dep/
  - 📄 SKILL.md 1.5 KB
- 📁 research/
  - 📄 SKILL.md 6.5 KB
- 📁 review/
  - 📄 SKILL.md 25.6 KB
- 📁 self-update/
  - 📄 SKILL.md 11.0 KB
- 📁 setup/
  - 📄 SKILL.md 8.6 KB
- 📁 tasks/
  - 📄 SKILL.md 3.7 KB
- 📁 uninstall/
  - 📄 SKILL.md 2.0 KB
📄 install.sh 18.4 KB
📄 SKILL.md 7.7 KB
📄 VERSION 6 B

SKILL.md

---
name: xavier
description: AI Agent Orchestrator & Knowledge System. Use when user says "/xavier setup", "/xavier review", "/xavier grill", "/xavier add-dep", "/xavier remove-dep", "/xavier deps-update", "/xavier uninstall", or any "/xavier" command.
---

# Xavier — AI Agent Orchestrator

Xavier is an AI agent orchestrator that manages code reviews with diverse personas, dependency-skill knowledge, and a personal knowledge vault.

## Command Routing

Parse the user's input to determine the subcommand. The argument after `/xavier` determines which skill to load and execute.

If no subcommand is provided, list available commands by scanning `<XAVIER_HOME>/skills/` for directories containing `SKILL.md`. Read each skill's YAML frontmatter and display a table with columns **Command** and **Description**.

### Router Lifecycle

Follow these steps exactly for every `/xavier <command>` invocation:

**0. Resolve XAVIER_HOME**: before doing anything else, determine the vault location:

- Run `echo "$XAVIER_HOME"` via Bash.
- If the variable is set and non-empty, use that value as the vault root.
- If unset or empty, default to `~/.xavier/`.
- Store the resolved path. **All `~/.xavier/` references below mean this resolved vault root.**

**1. Parse sub-command**: extract the first argument after `/xavier`. Any remaining arguments are passed through to the skill.

**2. Resolve skill file**: look for `<XAVIER_HOME>/skills/<command>/SKILL.md`.

**3. Unknown command gate**: if the skill file does not exist, show an error:

> Skill not found. Run `/xavier setup` to install skills.

**4. Read frontmatter**: parse the skill file's YAML frontmatter to get the `requires` list.

**5. Vault gate**: if `requires` is non-empty (not `[]`), check that `<XAVIER_HOME>/config.md` exists. If it does not exist, tell the user:

> Xavier vault not found. Run `/xavier setup` first.

Then stop — do not execute the skill.

**6. Resolve requires**:

**6a. Auto-load config**: Read and parse `<XAVIER_HOME>/config.md`. Make the config context available for all subsequent resolution steps. Validate that the following fields exist: `name`, `teams`, `git-strategy`, `adapter`. Warn (do not fail) on any missing fields.

**6b. Resolve adapter** (if `adapter` is in the requires list): Read the adapter name from the config's `adapter` field. Load the adapter from `<XAVIER_HOME>/references/adapters/<adapter-name>/adapter.md`. This is a sub-step of config resolution — the adapter key depends on the config being loaded first.

**6c. Resolve remaining keys**: For each other key in the `requires` list (excluding `config` and `adapter`, which are already resolved), load the corresponding context using the [Requires Vocabulary](#requires-vocabulary) below. Make all resolved context available for the skill's execution.

**7. Execute inline**: read the skill body (everything after the frontmatter) and follow its instructions directly in the current conversation, with all resolved context available.

**8. Vault commit**: after the skill completes successfully, dispatch a vault commit if the vault exists. Read the git strategy from `<XAVIER_HOME>/config.md`:

- **auto-commit** or **batch-commit**: `cd <XAVIER_HOME> && git add -A && git commit -m "<command>: <short context>"`
- **batch-commit + auto-push**: same as above, then `git push`
- **user-driven**: skip — the user commits manually

Skills never mention or execute vault commits — the router owns this exclusively.

---

## Requires Vocabulary

> **Path note:** All paths below are relative to the resolved `XAVIER_HOME` (see step 0 of the Router Lifecycle). When you see `<vault>/`, substitute the resolved vault root (e.g., `~/.xavier/` by default, or whatever `$XAVIER_HOME` resolved to).

The following 14 keys are the only valid values in a skill's `requires` list:


| Key                  | What to load                                                                                                                   |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| `config`             | Read `<vault>/config.md` — **auto-loaded** for any skill with non-empty requires                                               |
| `personas`           | Read all `.md` files in `<vault>/references/personas/` (or repo overrides from `.xavier/personas/` if present)                 |
| `shark`              | Read `<vault>/references/patterns/shark.md`                                                                                    |
| `adapter`            | Read the adapter from `<vault>/references/adapters/` matching the `adapter` field in config — resolved as a sub-step of config |
| `recurring-patterns` | Extract recurring patterns from the 10 most recent review notes in `<vault>/knowledge/reviews/` for the current repo           |
| `team-conventions`   | Read files in `<vault>/knowledge/teams/` matching the current repo or team                                                     |
| `repo-conventions`   | Read files in `<vault>/knowledge/repos/` matching the current repo                                                             |
| `prd-index`          | List all `.md` files in `<vault>/prd/` with titles and frontmatter                                                             |
| `tasks-index`        | List all `.md` files in `<vault>/tasks/` with titles and frontmatter                                                           |
| `skills-index`       | List all directories in `<vault>/skills/`                                                                                      |
| `deps-index`         | List all directories in `<vault>/deps/`                                                                                        |
| `vault-memory`       | Read `<vault>/MEMORY.md`                                                                                                       |
| `research-index`     | List all `.md` files in `<vault>/research/` with titles and frontmatter                                                        |


### Annotations: required vs optional

Requires keys support `:required` and `:optional` annotations to signal how the router should handle empty resolution:

```yaml
requires: [config, personas:required, recurring-patterns:optional]
```

- **Bare keys** (no annotation) default to `:required`.
- **`:required`** — the router warns when this key resolves to empty context (e.g., directory has no files). The skill still executes, but the user sees a diagnostic.
- **`:optional`** — the router silently provides an empty result when the key resolves to nothing. No warning.

### Rule: declare all vault-path reads

Skills MUST NOT read vault paths that are not covered by their `requires` list. Every vault directory a skill reads from must have a corresponding requires key declared in the frontmatter. Skills that only WRITE to a vault path (e.g., writing a new file to `tasks/`) do not need the corresponding index key — only skills that READ or LIST from those paths do.

If a `requires` key cannot be resolved (e.g., directory is empty or doesn't exist), provide an empty result for that key — do not fail. The skill decides how to handle missing context.

---

## Reference Files

Shared references used across multiple skills live in `<vault>/references/`:

- **`<vault>/references/patterns/shark.md`** — Shark orchestration protocol (delegates, never implements; backpressure is truth; remora spawning rules)
- **`<vault>/references/formats/zettelkasten.md`** — Base Zettelkasten frontmatter schema for vault notes
- **`<vault>/references/personas/`** — Default reviewer personas (correctness, security, performance)
- **`<vault>/references/adapters/`** — Runtime adapter contracts and implementations

Comments 0

Latest | Hot

Please login before commenting.

Loading comments...

xavier

Directory Structure

SKILL.md

Report

Notice