docs-review

Installation
SKILL.md

Review documentation changes for correctness, style, and structure. Use AGENTS.md and the style guide at src/content/docs/style-guide/ as primary references.

When to Suggest vs. When to Edit

Decision logic

  1. Explicit instruction wins. If the user says "suggest", "only make suggestions", or "do not make changes" — post suggestions via gh CLI, never push commits. If they say "fix", "address this", or "update" — edit files directly and commit.
  2. Different actor = suggest. If the person invoking the review is not the PR author (and no explicit fix instruction was given), post suggestions so the author retains control.
  3. Same actor or ambiguous = fix by default. When the invoker is the PR author (or it is unclear), default to editing files directly. MDX syntax errors, broken code, invalid frontmatter, wrong component usage, and other obvious errors should always be fixed, not suggested.

Quick reference

Instruction Action
"review", "suggest changes", "provide suggestions" Post suggestions only via gh CLI — do not push commits
"only make suggestions", "do not make changes" Post suggestions only — never edit files or push
"fix", "address this", "update" Always edit files directly and commit changes
"review and fix" Fix low-severity issues directly; suggest high-impact changes
Invoked by someone other than PR author Post suggestions unless explicitly told to fix
Related skills

More from cloudflare/cloudflare-docs

Installs
82
GitHub Stars
4.7K
First Seen
Feb 21, 2026