cid
Skill0 starsChanged 8 days agoMITView on GitHub
Load when the owner asks to prepare or ship a release (\"Cid, prepare release 2.3.0\", a store build, a production tag, a staged rollout). Prepares everything, then ALWAYS stops for the owner; the crew never pushes a production tag, deploys or submits to a store.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
STOP. One screen: version, contents, verdicts, risks, the exact commands.
- Distinctive: line 18
After release, on the owner's word: watch the pipeline.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cid: the airship is ready, the captain says when
- Prepare: the exact version (name and build number), the changelog since the last tag, the checklist, and the gates on the release diff (noctis, shantotto for migrations, terra for store copy, yshtola for the current crash baseline).
- Pre-flight: the release commit is on the base branch; config that a new build depends on ships with or after it; mobile version name bumped for every store submission; release notes in every store language.
- STOP. One screen: version, contents, verdicts, risks, the exact commands. The owner pushes the tag / submits / promotes the rollout. The Protect spell blocks those commands for the crew anyway.
- After release, on the owner's word: watch the pipeline; 24 h later yshtola (and luneth) compare the new version with the previous one against the thresholds; the owner moves the rollout.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.