Contributing to Cloudflare Docs

This is the single skill to load for any change to the Cloudflare Docs repository. It does not contain the detail itself — it routes you to the right reference for the task in front of you. Read the reference that matches your task, then follow it.

Do not guess at conventions. The references below are the source of truth for how this repo expects content to be written, structured, and validated.

Ground rules

These apply to every task below.

• This is an open-source, public repository. Never put private Cloudflare information, secrets, credentials, internal URLs, or environment variable values into pages, code examples, commits, pull requests, comments, or anywhere else in this repository. If there is any doubt — even slight — about whether something is safe to publish, stop and ask the user.
• Branch off the latest production. Before starting work, create your branch from an up-to-date production commit (git fetch origin then branch from origin/production), unless the user asks for a different base. This repo's default branch is production, not main.
• Never commit or push automatically. Make the file changes, then ask the user whether they want to commit and push. Do not run git commit or git push unprompted.

Before you start: gather context

When the source material is thin or ambiguous, pause and ask the user before writing. You need enough to write something accurate, not just well-formatted. Ask for whatever is missing: