cloud-routines

原文涵盖的主题

• Cloud routines
• 1. Compute the spec
• 2. The environment
• 3. The tracking issue
• 4. The routines
• 5. Delete
• Pause
• After a release

A repo that has a routine block in .github/pipeline.json gets up to three cloud routines (triage, build, and collect for the feedback repo) and one cloud environment. scripts/routine-spec.sh computes what to create. This skill creates it, with the maintainer's yes at each write. Summary: compute the spec, show it, let the maintainer save the setup script in the web UI, then create or update each routine with RemoteTrigger and compare with list. The settings come from .github/pipeline.json on the default branch of the repo. The printed setup script installs the pin, each --tags release, and each release listed in .claude-plugin/releases.txt on the default branch of the plugin repo (at most 3). --tags is for a release that the list does not hold, because one environment can serve several repos with different pins. A repo with no routine key prints an empty list and a note: make nothing, and tell the maintainer to add the block first. Never pass the JSON as a command-line argument; read it from the file. Show the maintainer, for each routine: the name, the schedule, the sources, the webhooks and the prompt. Do not print the whole setup script unless asked. The spec holds no secret and

这里只展示节选，请以完整原文和当前要求为准。