开发与测试
name: cf-cli
description: Use when the user asks for Cloudflare's
Cloudflare
cf-cli
Use when the user asks for Cloudflare's `cf` CLI, `cf cli search`, or `cloudflare.config.ts` to inspect resources, manage zones or DNS, attach domains, or deploy. Existing Wrangler projects keep their configured workflow unless migration is requested.
yan-labs · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add yan-labs/yan-skills --skill cf-cli技能说明
name: cf-cli
description: Use when the user asks for Cloudflare's cf CLI, cf cli search, or cloudflare.config.ts to inspect resources, manage zones or DNS, attach domains, or deploy. Existing Wrangler projects keep their configured workflow unless migration is requested.
Cloudflare cf CLI
cf 命令与覆盖范围会变化。以已安装版本和命令帮助为准,不把 Wrangler 参数直接套用。
Start with the installed CLI
- Check
cf --versionand the project's package manager, scripts, config, and any localcfor Wrangler dependency. Run project commands through the project's pinned version when present. For account-level work, the installed globalcfis fine. Cloudflare's announcement documentsnpm i -g cffor installation. - Run
cf cli search "<action and resource type>". Keep the query anonymous: no domains, account or resource IDs, names, email addresses, or tokens. Pick the relevant result; search can rank a similarly named product above the intended one. - Read
cf <discovered command> --help. For API request fields and response shape, runcf schema <discovered command without cf>. Read the specific Cloudflare documentation or API page when semantics or prerequisites matter. Do not infer flags from Wrangler. - If search misses a command, consult the official docs or inspect the exact command group once. Do not run a chain of nested
--helpcalls or guess a similarly named command.
Authenticate and select the target
- Check
cf auth whoamibefore remote operations. A Wrangler login does not establish acflogin. Usecf auth loginor an existing, appropriately scopedCLOUDFLARE_API_TOKEN; do not print, paste, log, or put token values in command arguments. If login opens a browser, follow the workspace's browser instructions. - Resolve the intended account, zone, project, Worker, hostname, and environment from the request and existing configuration before changing anything. Use a named
cfprofile or account setting when several accounts are available. - Read results are safe to inspect; for mutations, review the exact target and required permissions. Use a command's
--dry-runwhen available, then verify the remote result separately. A dry run is not deployment or domain activation.
Choose the right workflow
- Existing Wrangler project: keep its current build and deployment path unless migration is requested.
cf migratechanges project configuration; inspect the diff and test before switching. 如cf当前版本将构建委托给 Wrangler,按已安装命令与项目脚本执行。 Use the installed Wrangler skill for commands that remain on Wrangler. - New
cfproject: usecf initand the generatedcloudflare.config.ts; read the generated config and framework integration beforecf dev,cf build, orcf deploy. Do not manually copy awrangler.jsoncshape into the TypeScript config. - Zone onboarding: discover and inspect
cf zones listandcf zones create. Zone creation returns a pending zone; activation still requires the domain's nameservers or the documented partial-zone verification. Check existing zones, DNSSEC, and account scope before creating one. - Pages custom domain: discover and inspect
cf pages projects domains createfor the project/domain association. DNS and nameserver requirements depend on whether it is an apex domain, subdomain, and Cloudflare-managed zone. Association and DNS must both be verified. See Pages custom domains. - Worker custom domain: inspect the project's current routing config.
cloudflare.config.tscan declare a fetch trigger; existing Wrangler projects can userouteswithcustom_domain: true. An active Cloudflare zone and Worker are required, and a conflicting CNAME prevents attachment. Verify the deployed domain and live response. See Worker custom domains. - DNS only: discover
cf dns recordscommands, inspect the exact record before a write, and read it back afterward. A DNS record alone does not attach a Pages or Worker project.
Finish
Report the CLI version, account/resource/environment targeted, what changed, and what was actually checked. Keep CLI output and credentials separate; never turn a successful command, dry run, returned URL, or DNS record into a claim that the site works without a live readback.