Reviews

reviews/ defines project checks for code-review bots, such as dependency boundaries, error handling, and migration risks. One review spec writes that guidance into each bot's own file:

Other tools report review specs as unsupported.

Ellipsis takes the reviewer, its model, and any posting rules from x-ellipsis in a settings spec. Without a reviewer, sync writes no file and says what is missing.

Write one

agnostic-ai new review code-quality

It creates .agnostic-ai/reviews/code-quality.md. Write the checks the bot should apply, then sync and start a review. The spec supplies guidance only; it does not install or start a bot.

---
scope: backend
---

Flag any handler that talks to the database directly instead of going through a repository.

Reviews follow scope and the folder layout like rules. Specs with the same scope are joined into one file, without frontmatter. The Codex section sits in AGENTS.md, so every tool that reads AGENTS.md loads it, unless a targets: filter leaves out codex.

Include a file

Use a line containing only @path to include a project file. Paths start at the project root. For example, a folder's README.md can supply its review guidance:

---
scope: services/billing
target: cursor
---

@services/billing/README.md

• Sync writes the file's text in place of the line, so a README change shows up in sync --check.
• A missing file, an absolute path, or a path outside the project fails the load (AAI-001).
• A line inside a fenced code block stays as written.
• An included file is not searched for more @path lines.
• Only reviews take @path lines. On AGNOSTIC_AI.md the resolve-imports setting controls them.