---
name: brush-up
description: Repeatedly review and improve a document or skill to make it concise, complete, and polished.
argument-hint: "<topic>"
---

# Brush Up

Repeatedly review and improve the specified document, section, or skill. Continue until the review finds no more issues.

## Quick Start

Specify the target for review in `<topic>`. This can be a file path, document name, section name, skill name, etc.

```sh
/brush-up "Knowledge Bundles" section of docs/AGENTS.md
/brush-up IRIS.md
/brush-up .agents/skills/brush-up/SKILL.md
```

## Workflow

1.  Review from the following perspectives:
    -   Accuracy: Are there any factual errors or contradictions?
    -   Clarity: Can it be interpreted unambiguously? Are there any vague terms or undefined jargon?
    -   Consistency: Are identical concepts represented by different terms? Are there variations in spelling or notation?
    -   Completeness: Is all necessary information (such as prerequisites and parameters) present?
    -   Conciseness: Can redundant parts be removed to make it simpler and easier to understand?
    -   Wording/Phrasing: Are there any typos, omissions, or unnatural expressions?
    -   Appropriateness: Is the content aligned with the purpose and scope of the document? Does it overlap with the role of other documents?
2.  If you find issues or improvements, keep track of them internally, but **present them to the user one by one**. Do not list them all at once.
3.  For the current item, classify it into a confirmation level 🔴 (Critical), 🟡 (Issue), or 🟢 (Minor). Present the item using `<Confirmation Level> <Summary>` as a heading, followed by specific suggestions for improvement and a predicted diff for that item immediately below it. Ask the user how they would like to address it (e.g., apply the change, skip, or modify).
4.  Once the user responds and the current item is addressed (applied, skipped, or modified), proceed to the next item and repeat step 3.
5.  Repeat this process until all identified issues and improvements are resolved. Do not conclude the brush-up process until all items are processed.
6.  Once all items are resolved, return to step 1 to perform another review pass on the updated document, and repeat until no more issues are found.

## Notes

-   When the user asks for your opinion, state a clear recommendation or view. Avoid vague responses like "either is fine."
-   Respect the user's suggestions and decisions unless there is a clear issue (such as factual errors or rule violations).
