quality-review-documentation

quality-review-documentation is a cursor rule for Cursor from oakensoul/nextjs-cursor-prompts. It costs 0 tokens per session (4,249 once invoked), scanned A, original, MIT.

A set of instructions for reviewing project documentation, including technical guides, user help, API references, and maintenance notes. It checks completeness, accuracy, organization, usability, and upkeep.

In plain words
What is it for?
Use it to inventory documentation files and assess how well different readers can understand and use the project's documentation.
Why use it?
It helps reveal missing, unclear, outdated, or difficult-to-find documentation and turns those findings into improvement suggestions.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it to inventory documentation files and assess how well different readers can understand and use the project's documentation.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/oakensoul/nextjs-cursor-prompts/quality-review-documentation
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/oakensoul/nextjs-cursor-prompts

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for quality-review-documentation

README.md
[![agentmods](https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/quality-review-documentation/github.svg)](https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/quality-review-documentation)
Your own site
<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/quality-review-documentation"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/quality-review-documentation/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for quality-review-documentation

Your own site · 80×15
<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/quality-review-documentation"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/quality-review-documentation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 4,249 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.04249
Opus 5 $0.00000 $0.02124
Sonnet 5 $0.00000 $0.00850
Haiku 4.5 $0.00000 $0.00425

Measured 8d ago against content hash 221ad5b362e2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

quality-review-documentation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/prompts/quality/quality-review-documentation.mdc · 523 lines

How it starts

The opening of the file, as written. The whole thing — 523 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Documentation Quality Review and Assessment

This prompt provides comprehensive evaluation of project documentation including technical docs, user guides, API documentation, and maintenance materials with actionable improvement recommendations.

🎯 DOCUMENTATION REVIEW OBJECTIVES:

  1. ASSESS documentation completeness across all project areas
  2. EVALUATE content quality including accuracy, clarity, and usefulness
  3. REVIEW structure and organization for logical flow and discoverability
  4. VALIDATE user experience from different audience perspectives
  5. IDENTIFY maintenance gaps and sustainability issues

📚 DOCUMENTATION INVENTORY AND ANALYSIS:

STEP 1: Documentation Discovery and Categorization

Automated Documentation Inventory:
# Discover all documentation files
echo "📋 Discovering project documentation..."

# Find markdown files
echo "## Markdown Documentation:"
find . -name "*.md" -not -path "./node_modules/*" -not -path "./.git/*" | sort

# Find documentation directories
echo -e "\n## Documentation Directories:"
find . -type d -name "*doc*" -o -name "*guide*" -o -name "*manual*" | grep -v node_modules | sort

# Find README files
echo -e "\n## README Files:"
find . -name "README*" -not -path "./node_modules/*" | sort

# Find API documentation
echo -e "\n## API Documentation:"
find . -name "*.yaml" -o -name "*.yml" -o -name "swagger*" -o -name "openapi*" | grep -v node_modules | sort

# Find JSDoc/TypeDoc files
echo -e "\n## Code Documentation:"
find . -name "*.jsdoc" -o -name "typedoc.json" | grep -v node_modules | sort

# Check for documentation generators
echo -e "\n## Documentation Tools:"
[ -f "package.json" ] && grep -E "(jsdoc|typedoc|docusaurus|vitepress|gitbook)" package.json || echo "No documentation tools found in package.json"
Documentation Categories Assessment:
## Documentation Categories Checklist

### Project Overview Documentation:
- [ ] **Main README.md** - Project introduction and quick start
- [ ] **CONTRIBUTING.md** - Contribution guidelines
- [ ] **CHANGELOG.md** - Version history and changes
- [ ] **LICENSE** - Legal and usage terms
- [ ] **CODE_OF_CONDUCT.md** - Community guidelines

### Technical Documentation:
- [ ] **Architecture Documentation** - System design and structure
- [ ] **API Documentation** - Endpoint specifications and examples
- [ ] **Database Schema** - Data model and relationships
- [ ] **Deployment Guides** - Installation and deployment procedures
- [ ] **Configuration Guides** - Environment setup and options

### User Documentation:
- [ ] **User Guides** - End-user instruction manuals
- [ ] **Tutorials** - Step-by-step learning materials
- [ ] **FAQ** - Frequently asked questions
- [ ] **Troubleshooting** - Problem resolution guides
- [ ] **Examples** - Working code samples and demos

### Developer Documentation:
- [ ] **Setup Instructions** - Development environment setup
- [ ] **Coding Standards** - Style guides and conventions
- [ ] **Testing Documentation** - Testing strategies and procedures
- [ ] **Security Guidelines** - Security best practices
- [ ] **Performance Guidelines** - Optimization recommendations

### Operational Documentation:
- [ ] **Monitoring Guides** - System monitoring and alerting
- [ ] **Backup Procedures** - Data backup and recovery
- [ ] **Disaster Recovery** - Business continuity plans
- [ ] **Runbooks** - Operational procedures
- [ ] **Incident Response** - Emergency response procedures

Read the full file on GitHub · 523 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 523 lines · 0 tokens per session scan A 221ad5b362e2

Subscribe to this mod's changes

quality-review-documentation is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,249 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.