Code reviewer

Code reviewer — a demo bundle for the ADI Store

An agent that reads a diff the way a senior engineer does: what would break, which line, and then it stops.

It is here to be read as much as to be run. This is the smallest thing a marketplace item can be — one agent and nothing else — so it is the file to copy when you want to publish one of your own. Install it with a click from the ADI Store, or:

adi-mono marketplace install store/reviewer

What makes this a bundle

Nothing but the directory it is in. A marketplace item is a git repository whose top level holds one directory per kind of element, and this one holds agents/:

agents/
  reviewer.toml     # one agent, named by its filename

The eight kinds are agents/, tools/, dashboards/, llm/, embeddings/, services/, triggers/ and project/. A repository may carry any of them; the installer reads what is actually there rather than trusting the manifest, and an element can be installed on its own:

adi-mono marketplace install store/reviewer/agents/reviewer

What is in the agent

reviewer.toml is an ordinary agent definition — the same file adi-mono agents save writes:

• backend = "harness:adi" — the loop it runs in.
• system_prompt — the whole of what makes it a reviewer rather than a chat.
• [[secrets]] — it declares REVIEWER_GITHUB_TOKEN. Declaring is not having: the install

lands the agent with the secret named and unset, and the panel says so on the row. Nothing is read from your machine and nothing is filled in for you.

Publishing one of your own

1. Put your elements in kind directories at the root of a repository, as above.
2. Push it, and take the commit: git rev-parse HEAD.
3. Add an entry to a marketplace manifest naming that repository and that full 40-hex commit.

The pin is the point: what somebody read is what installs, and moving onto a newer commit is marketplace update, an act they take.

The format, and every rule the installer enforces, is in docs/marketplace.md.

What it does not do

Nothing runs on arrival. An installed agent is a definition on your disk until you run it, and this one has no trigger, no service and no schedule — there is nothing here that starts itself.