changelog
Creates, updates, and reviews product changelog entries for the Cloudflare documentation site. Load when generating changelog MDX files, editing existing entries, reviewing changelog style, or validating frontmatter.
- Installs
- 96
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/cloudflare/cloudflare-docs --skill changelog- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads changelog automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Use this skill when creating, editing, or reviewing changelog entries under src/content/changelog/.
Style reference: .agents/references/style-guide.md contains the canonical rules for writing style, formatting, links, code blocks, and frontmatter. The changelog-specific additions below extend those rules — they do not replace them.
Prerequisites
You need three things before writing:
- A product name (for example, Workers, KV, Hyperdrive, Containers, R2)
- A description of the change being documented
- Enough context to explain the "why" and use cases
If any are missing, ask for clarification. Do not proceed without all three.
Determine the product folder
Use the product name to find the correct folder under src/content/changelog/{product}/. Check existing folders for valid product names — do not guess.
Create the changelog file
Path format:
src/content/changelog/{product}/{YYYY-MM-DD}-{useful-short-name}.mdx
Use today's date and a concise, hyphenated slug describing the change.
Frontmatter
---
title: <TITLE>
description: <ONE_SENTENCE_SUMMARY>
products:
- <PRODUCT>
date: <YYYY-MM-DD>
---
Writing style
Follow the rules in .agents/references/style-guide.md. Changelog-specific additions:
- Opening sentence: what the feature/change is and what problem it solves
- Expand on usage, use cases, and the "why" in subsequent paragraphs
- Assume a technical developer/cloud audience
Code examples
Include a code example when the changelog describes an API, SDK, or configuration change.
- Keep snippets short and focused on the new feature — minimize boilerplate
- Import components after the frontmatter:
import { TypeScriptExample, WranglerConfig } from "~/components"; - Workers JS/TS → use
TypeScriptExample(not barejs/tsfences) - Wrangler config → use
WranglerConfigwith TOML input and$todayforcompatibility_date(not baretoml/jsoncfences) - Other languages (Python, Rust, Go, etc.) → use a plain fenced code block with the correct language identifier
- Non-Workers config snippets (JSON, YAML, etc.) → use a plain fenced code block (
json,yaml, etc.)
Documentation links
End the changelog with a link to relevant documentation:
- Use relative paths (for example,
/workers/configuration/placement/) - Link text must describe the destination — never "click here" or "read more"
- Check for uncommitted/staged
.md/.mdxfiles that might be the related documentation
Reference examples
Review these existing changelogs for style and format guidance:
src/content/changelog/workers/- Workers changelogs with code examplessrc/content/changelog/kv/- KV changelogssrc/content/changelog/hyperdrive/- Hyperdrive changelogssrc/content/changelog/containers/- Container changelogs
Read 2-3 entries from the target product's changelog folder before writing to match style and depth. If the target folder has fewer than 2 entries, read from the folders listed above as a reference.
Editing existing entries
When updating an existing changelog entry, preserve the original structure and voice. Apply only the requested changes — do not rewrite surrounding content.
Reviewing changelog entries
When reviewing, validate against every section above: frontmatter fields, file path conventions, writing style, code example quality, and documentation links. Flag issues by severity:
- Error: Missing required frontmatter fields, wrong product folder, broken links
- Warning: Style violations, missing code examples for API changes, vague descriptions
- Nit: Minor phrasing improvements
Output
Create or update the changelog file and show the complete file path and content.
FAQ
What does the changelog skill do?
Creates, updates, and reviews product changelog entries for the Cloudflare documentation site. Load when generating changelog MDX files, editing existing entries, reviewing changelog style, or validating frontmatter.
How do I install changelog?
Run npx skills add https://github.com/cloudflare/cloudflare-docs --skill changelog in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/changelog/ (personal) or .claude/skills/changelog/ (project).
Which AI agents can use changelog?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is changelog safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains changelog?
It is published by cloudflare in cloudflare/cloudflare-docs, and it is an official skill from the maker of the technology it covers. It has 96 recorded installs.
More from cloudflare/cloudflare-docs
eli5
cloudflare/cloudflare-docs
Transform technical jargon into clear explanations using before/after comparisons, metaphors, and practical context
code-review
cloudflare/cloudflare-docs
Review the changed lines of a single file in a pull request for bugs, correctness, error handling, security, and maintainability, and return structured findings.
cloudflare
cloudflare/cloudflare-docs
Open the skill to read its SKILL.md instructions.
docs-review
cloudflare/cloudflare-docs
Reviews documentation PRs and provides GitHub PR suggestions. Load when asked to review, suggest changes, or provide feedback on docs content. Covers MDX, frontmatter, style guide, components, and content accuracy.
wrangler
cloudflare/cloudflare-docs
Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices.
durable-objects
cloudflare/cloudflare-docs
Create and review Cloudflare Durable Objects. Use when building stateful coordination (chat rooms, multiplayer games, booking systems), implementing RPC methods, SQLite storage, alarms, WebSockets, or reviewing DO code for best practices. Covers Workers integration, wrangler config, and testing with Vitest.
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.