---
title: "trove items, review"
description: "Use when you look after a team book and go through the fixes and reader requests that wait on you, when you send a fix for a chapter you cannot edit, or when you read the history of a book."
url: https://docs.heytrove.ai/reference/cli/items-review
updated: 2026-11-03
---

# trove items, review

> Load this page when: you need to see what waits on you in team books, send or answer a suggested fix, or read who changed a book

## For agents

- Run trove items review to see the fixes and reader requests that wait on the user. Take one item at a time and ask the user what to do.
- Send a fix for a chapter you cannot edit with trove items suggest. A fix needs a reason.
- Add a fix with trove items approve. Add -f FILE to change the text first. Say why a fix is not added with trove items decline and a reason.
- Answer a reader request with trove items put and --fixes GAP_ID. The request closes when the write succeeds.

These commands are for team books. A team book has people who look after it. See [Teams](https://docs.heytrove.ai/concepts/teams.md). Other writing commands are on [trove items: write](https://docs.heytrove.ai/reference/cli/items-writing.md). Reader requests are on [trove items: gaps](https://docs.heytrove.ai/reference/cli/items-gaps.md).

## Quick reference

| Command | Who runs it | What it does |
| --- | --- | --- |
| `trove items review` | Anyone in a team | List what waits on you |
| `trove items suggest` | Any team member | Send a fix for one chapter |
| `trove items suggestion` | Proposer or caretaker | Show one fix and its change |
| `trove items approve` | Owner or maintainer of the chapter | Add a fix to the chapter |
| `trove items decline` | Owner or maintainer of the chapter | Do not add a fix, and give a reason |
| `trove items withdraw` | Proposer | Take back your own open fix |
| `trove items dismiss-gap` | Owner or maintainer | Dismiss a reader request |

## trove items review

Lists the fixes and reader requests that wait on you. The oldest item is first. Without `--book`, the call marks every new item as seen, so the count of new items on the Team page goes to zero. With `--book`, it marks only the items of that book. The call with `--sent` does not mark anything.

**Usage**

```bash
trove items review [--all | --sent] [--book ID] [--json]
trove items review --counts [--json]
```

**Arguments and flags**

| Flag | Value | Default | Meaning |
| --- | --- | --- | --- |
| `--all` | none | off | Show also the items on chapters that you do not look after. These items are read-only. Each one shows who it waits on. |
| `--sent` | none | off | Show the fixes that you sent, and what happened to each. |
| `--book` | id | none | Show one book only. |
| `--counts` | none | off | Print only the counts. Cannot combine with other flags. |

**Output**

```terminal
3 waiting on you (1 reader request, 2 suggested fixes).
[fix] cmfix01  Team Handbook › Deploying to Production — "Add the rollback command we use" — Noa Helper via Claude Code, 2 days  fixes 1 request
[request] cmgap01  Team Handbook › Deploying to Production — "Holiday deploy freeze" — 1 reader, first asked 3 days
Open a fix: trove items suggestion <id> · Answer a request: trove items put <book>:<page> -f <file> --fixes <gapId>
```

A fix is marked `stale` when the chapter changed after the fix was written. With `--json`, the output is the server reply. See the [Review API](https://docs.heytrove.ai/reference/api/review.md).

## trove items suggest

Sends a fix for one chapter to the people who look after it. Use it when you cannot edit the chapter. The chapter does not change until one of them adds the fix.

**Usage**

```bash
trove items suggest BOOK:PAGE --reason TEXT [--file FILE] [--fixes GAP_ID ... | --no-fixes]
```

**Arguments and flags**

| Argument or flag | Value | Default | Meaning |
| --- | --- | --- | --- |
| `BOOK:PAGE` | id and a page number or chapter slug | required | The chapter to fix. |
| `--file`, `-f` | path | stdin | The new text of the whole chapter: one page, or several pages each starting with its own `# ` heading, to split the chapter. When you edit a page that is over the limit, split it as part of the edit: send the page again as several pages, each starting with its own "# " heading, in one page write. |
| `--reason` | text | required | Why the chapter needs the change. Up to 1,000 characters. |
| `--fixes` | one or more request ids | none | Open reader requests that this fix answers. Up to 20. Each must be open on this book. Get the ids with `trove items gaps BOOK --json`. They close when the fix is added. Pass this or `--no-fixes`: with neither, and open requests on the chapter, the command sends nothing and lists them. |
| `--no-fixes` | none | off | The fix answers no open reader request. Cannot be used with `--fixes`. |

**Example**

```bash
trove items suggest cmabc123:3 -f chapter3.md --reason "Add the rollback command we use" --fixes cmgap01
```

**Output**

```terminal
I sent Dana a fix for "Deploying to Production" in "Team Handbook".
Suggestion cmfix01.
```

## trove items suggestion

Shows one fix: its state, the chapter, who sent it, the reason and the change as a diff. When the chapter changed after the fix was written, the output says so and shows the redo command.

**Usage**

```bash
trove items suggestion ID [--json]
```

## trove items approve

Adds a fix to the chapter. The book gets a new version. The version history names the person who wrote the fix and the person who added it. The readers whose requests the fix answers get a message.

**Usage**

```bash
trove items approve ID [--file FILE] [--note TEXT] [--expect-version N]
```

**Arguments and flags**

| Argument or flag | Value | Default | Meaning |
| --- | --- | --- | --- |
| `ID` | suggestion id | required | The fix to add. |
| `--file`, `-f` | path | none | Your own text for the chapter. The history shows "added with changes". |
| `--note` | text | none | A note for the person who sent the fix. Up to 1,000 characters. |
| `--expect-version` | integer | none | The book version that you based your text on. |

When the chapter changed after the fix was written, `approve` without `--file` is refused with `SUGGESTION_STALE`. Redo the fix on the current text. Then run `approve` again with `-f` and `--expect-version`.

**Output**

```terminal
Added the fix to "Deploying to Production" (version 4).
Closed 1 reader request.
```

## trove items decline

Does not add a fix. The person who sent it sees your reason.

**Usage**

```bash
trove items decline ID --reason TEXT
```

The reason is required. It is up to 1,000 characters.

## trove items withdraw

Takes back a fix that you sent, while it is open. Nobody else can withdraw it.

**Usage**

```bash
trove items withdraw ID
```

## trove items dismiss-gap

Dismisses a reader request on a book that you look after. The request leaves the list.

**Usage**

```bash
trove items dismiss-gap BOOK --subcategory TEXT
```

## Answer a reader request

Write the answer into the chapter and link the request. Use `--fixes` with `trove items put`:

```bash
trove items put cmabc123:3 -f chapter3.md --fixes cmgap01
```

When the write succeeds, the linked requests close and the readers get a message. If you cannot edit the chapter, use `trove items suggest` with `--fixes`. The requests close when someone adds the fix.

## Version history

```bash
trove items history BOOK [--diff VERSION] [--json]
```

Without `--diff`, the command lists every version with the person who wrote it, the person who added it, and the reader requests it answered. With `--diff`, it prints what changed in that version.

| Who | What they see |
| --- | --- |
| Uploader and book owners | Every version. They can restore. |
| Book maintainers | Every version. They cannot restore. |
| Owners and maintainers of a chapter | The versions that changed their chapters. |
| Other members and people who sent a fix | No versions. |

## Errors

| Code | Meaning | Fix |
| --- | --- | --- |
| `SUGGESTION_STALE` | The chapter changed after the fix was written. | Redo the fix on the current text. Run `approve` with `-f` and `--expect-version`. Pass `--expect-version` whenever you pass `-f`. |
| `ALREADY_DECIDED` | Someone already decided this fix. | Run `trove items suggestion ID` to see the result. |
| `OWN_SUGGESTION` | You cannot add your own fix. | Ask another owner or maintainer. |
| `NOT_PROPOSER` | Only the person who sent a fix can withdraw it. | None. |
| `CHAPTER_GONE` | The chapter no longer exists. | Say why the fix is not added. |
| `TOO_MANY_OPEN_FIXES` | You already have many fixes waiting. | Withdraw some, or wait until they are answered. |
| `HISTORY_DENIED` | You do not look after this book or chapter. | Ask the people who look after it. |

REST equivalent: [Review API](https://docs.heytrove.ai/reference/api/review.md).
