| name | review-note |
| description | Review a KB note or guide for quality, clarity, and completeness |
| allowed-tools | Read Bash(grep *) Bash(wc *) Bash(find *) |
| arguments | ["path"] |
Review KB Note
Review the note at $ARGUMENTS.path for the following criteria:
Content Quality
- Clarity: Is the content clear and easy to follow?
- Completeness: Are steps complete? Are there missing prerequisites or assumptions?
- Accuracy: Do commands and configurations look correct?
- Structure: Does it follow a logical flow (context, prerequisites, steps, verification, troubleshooting)?
Writing Quality
- Grammar and spelling: Flag any errors
- Consistency: Consistent use of terminology, formatting, and voice
- Code blocks: Are they properly fenced with language tags?
- Links: Are references and links present where needed?
Actionability
- Copy-paste ready: Can a reader follow the guide end-to-end?
- Environment assumptions: Are environment variables and prerequisites clearly stated?
- Verification steps: Does each major step include a way to verify success?
Provide a summary with:
- Overall quality rating (draft / needs-work / good / polished)
- Top 3 issues to fix
- Suggested improvements (if any)
