Creates and updates GitHub pull requests for cloudflare-docs changes. Load when asked to open, create, submit, update, edit, or write a title or description for a PR. Covers title conventions, PR body structure, and the documentation checklist template.
Use this skill when creating a GitHub pull request for changes to this repository, or when editing an existing PR's title or description.
gh CLIThis skill uses the gh CLI throughout. If a gh command fails because it is not installed or not authenticated, fall back to providing the PR title and body clearly so the user can copy-paste them, along with the relevant GitHub URL:
https://github.com/cloudflare/cloudflare-docs/compare/production...<branch> (get branch from git branch --show-current)https://github.com/cloudflare/cloudflare-docs/pull/<number> — instruct them to select Edit on the description.When asked to update or edit an existing PR description (or title), follow these rules strictly — then stop. Do not proceed to the "Creating a new PR" steps below.
gh pr view <number> --json title,body before making any changes.gh pr edit <number> --title "..."gh pr edit <number> --body-file /tmp/pr-body.md and clean up with rm /tmp/pr-body.md. Do not use --body "..." — shell quoting mangles backticks and other Markdown formatting.Follow Steps 1–4 below only when creating a new PR (or when an existing PR has an empty description).
Run --stat first to understand the scope without blowing up context:
git log --oneline production..HEAD
git diff production...HEAD --stat
If the stat output shows more than ~20 files changed, do not run the full diff. Instead, read specific files that are unclear from the stat output. For smaller changesets (under ~20 files), the full diff is fine:
git diff production...HEAD
productionThis repo uses production as the default branch, not main. Always use --base production when creating PRs. Contributors from other repos often expect main — this is intentional.
For content changes, the dominant convention is product brackets:
[Product] Short description
For changes spanning multiple products:
[Product1, Product2] Short description
For non-content changes (tooling, CI, config, components, worker code, repo maintenance), use a conventional commit prefix instead: