Repo Mirror Sources
netdata/netdata
Inspect Netdata-org source checkouts under NETDATAREPOSDIR, or set up and synchronize that mirror when requested.
Roll a release back for real when post-deploy regression goes red — apc release rollback flips the current version to pulled and the last good version back to current in the release ledger, and…
Install Release Rollback
$ npx skills add Prismer-AI/PrismerCloud --skill release-rollback -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Prismer-AI/PrismerCloud release-rollback --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Prismer-AI/PrismerCloud.git skills-src && mkdir -p .claude/skills && cp -r skills-src/sdk/apc/skills/release-rollback .claude/skills/release-rollback && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "release-rollback" agent skill from https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/apc/skills/release-rollback into .claude/skills/release-rollback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-rollback", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/apc/skills/release-rollbackType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Prismer-AI/PrismerCloud --skill release-rollback -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Prismer-AI/PrismerCloud release-rollback --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Prismer-AI/PrismerCloud.git skills-src && mkdir -p .agents/skills && cp -r skills-src/sdk/apc/skills/release-rollback .agents/skills/release-rollback && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-rollback" agent skill from https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/apc/skills/release-rollback into .agents/skills/release-rollback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-rollback", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Prismer-AI/PrismerCloud --skill release-rollback -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Prismer-AI/PrismerCloud release-rollback --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Prismer-AI/PrismerCloud.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/sdk/apc/skills/release-rollback .cursor/skills/release-rollback && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-rollback" agent skill from https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/apc/skills/release-rollback into .cursor/skills/release-rollback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-rollback", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Prismer-AI/PrismerCloud.git --path sdk/apc/skills/release-rollback--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Prismer-AI/PrismerCloud --skill release-rollback -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Prismer-AI/PrismerCloud release-rollback --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Prismer-AI/PrismerCloud.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/sdk/apc/skills/release-rollback .gemini/skills/release-rollback && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-rollback" agent skill from https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/apc/skills/release-rollback into .gemini/skills/release-rollback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-rollback", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Prismer-AI/PrismerCloud release-rollbackInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Prismer-AI/PrismerCloud --skill release-rollback -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Prismer-AI/PrismerCloud.git skills-src && mkdir -p .github/skills && cp -r skills-src/sdk/apc/skills/release-rollback .github/skills/release-rollback && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-rollback" agent skill from https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/apc/skills/release-rollback into .github/skills/release-rollback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-rollback", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Prismer-AI/PrismerCloud --skill release-rollback -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Prismer-AI/PrismerCloud release-rollback --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Prismer-AI/PrismerCloud.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/sdk/apc/skills/release-rollback .opencode/skills/release-rollback && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-rollback" agent skill from https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/apc/skills/release-rollback into .opencode/skills/release-rollback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-rollback", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release-rollback- GitHub stars
- 1.6k
- Token cost
- ~2.2k tokens
- SKILL.md length
- 535 words
- Files
- 2
- Skills in repo
- 88
- Repo updated
- First seen
- Licence
- MIT
At a glance
Roll a release back for real when post-deploy regression goes red — apc release rollback flips the current version to pulled and the last good version back to current in the release ledger, and…
- Works in 4 steps: 备好 release 账本（本机替身） → dry-run：出回滚计划（不带 --approved） → 审批后执行（带 --approved）—— 真写账本 → …
- DevOps & Cloud work in your project
- SKILL.md covers 承重纪律（发版 skill 的命根子，先记死）, Anti-pattern（直接判红）, 工具契约（签名以此为准） and Workflow, plus 7 more sections
- Calls npx and git; needs APPROVAL_TOKEN
What it does
Release Rollback is an agent skill from Prismer-AI/PrismerCloud. Roll a release back for real when post-deploy regression goes red — apc release rollback flips the current version to pulled and the last good version back to current in the release ledger, and (with --mirror) repoints the bare mirror ref. Behind an approval gate; with no previous good version it BLOCKS instead of spinning green. green(0) applied · staged(3) plan awaiting approval · blocked(1) nothing to roll back to.
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `skill.json`). Compatibility notes: ["claude-code"]
It sits in DevOps & Cloud. It works with Git. The licence is MIT.
When your agent uses it
- DevOps & Cloud work in your project
Example prompts
- “/release-rollback”
Requirements
- Node.js
- A credential in APPROVAL_TOKEN
- Compatibility (from SKILL.md): ["claude-code"]
- Pre-approved tools (allowed-tools): Bash
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit e5d9444. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npxgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
APPROVAL_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
["claude-code"]
From compatibility in the SKILL.md frontmatter.
Context cost
Release Rollback loads about 2.2k tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 535 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Prismer-AI/PrismerCloud at commit e5d9444, republished under its MIT licence (© Prismer-AI). 535 words, ~2,214 tokens.
Download SKILL.mdSave it as
.claude/skills/release-rollback/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- release-rollback
- description
- Roll a release back for real when post-deploy regression goes red — apc release rollback flips the current version to pulled and the last good version back to current in the release ledger, and (with --mirror) repoints the bare mirror ref. Behind an approval gate; with no previous good version it BLOCKS instead of spinning green. green(0) applied · staged(3) plan awaiting approval · blocked(1) nothing to roll back to.
- allowed-tools
- Bash
- compatibility
- ["claude-code"]
- license
- MIT
- scope
- coding
- metadata.category
- release
release-rollback
上线后回归红时的真回滚（apc/01 §2 release-rollback，收口步 10）。它落两个真副作用：
- release 账本回退：把当前
current版本翻pulled、上一好版本翻回current（真写 JSON ledger，可读回核验）。 - 版本指针回退（给了
--mirror）：把 bare mirror 的refs/heads/release-current重指到上一好 tag 的 commit（真 git 副作用，git ls-remote可核验）。
什么时候用：release-verify（部署后回归）红了，需要把 fleet 退回上一个好版本。回滚后应建 bug task 回 bugfix 入口。
承重纪律（发版 skill 的命根子，先记死）
- 审批门不可跳。未审批 =
staged（出回滚计划 dry-run，不执行）。本机替身以--approved <token>非空为门（真 approvalId 服务端校验 = M5）。审批人看到的是回滚计划（from→to 版本 + 影响面），不是"agent 说要回滚了"。 - 无上一好版本 →
blocked，绝不空转返绿。账本只有一条、或更早的都已pulled⇒ 无从回滚 ⇒ blocked（exit 1）。这是本 verb 的负控注入点：一个"回滚"skill 若在没东西可回滚时也返绿，就是开卷考试。 - prod 不做。本 skill 是 test 环境的回滚；prod 回滚走人 + M5 路径。
Anti-pattern（直接判红）
- ❌ 无上一好版本时硬造一个"回滚成功"。planRollback
ok:false就是 blocked，别放松。 - ❌ 拿到
staged（计划）就以为已回滚。staged 是"等审批"，账本还没改。 - ❌ 手工改 ledger JSON /
git update-ref绕过 verb 的审批门和 plan 计算。
工具契约（签名以此为准）
apc不在 PATH——在仓库根用npx tsx sdk/apc/bin/apc.ts <sub>。
| 命令 | 作用 | 退出码 |
|---|---|---|
npx tsx sdk/apc/bin/apc.ts release rollback [--ledger <path>] [--mirror <bare>] [--approved <token>] [--json] | 算回滚计划 → 审批门 → 写账本回退（+ 可选 mirror ref 重指） | 0 green（applied）· 3 staged（计划待审批）· 1 blocked（无上一好版本） |
--json 字段（名以此为准）：
- 顶层：
{ verb:'rollback', decision, ledgerPath, plan, approved, applied, mirrorRepointed, blockers:[], notes:[] } plan：{ ok:true, from:{version,tag,status}, to:{version,tag,status}, next:[...] }或{ ok:false, reason }- ledger 条目形状：
{ version, tag, status:'current'|'pulled'|'superseded', ts }（current唯一）
Workflow
1. 备好 release 账本（本机替身）
账本记录发过的版本序列，当前版本 status:'current'。本机替身用一份 JSON（真 release-status 行的替身）：
cat > /tmp/apc-rollback-ledger.json <<'JSON'
[
{ "version": "2.0.5", "tag": "k8s-test-20260720-v2.0.5", "status": "superseded", "ts": "2026-07-20T00:00:00Z" },
{ "version": "2.0.6", "tag": "k8s-test-20260722-v2.0.6", "status": "superseded", "ts": "2026-07-22T00:00:00Z" },
{ "version": "2.0.7", "tag": "k8s-test-20260724-v2.0.7", "status": "current", "ts": "2026-07-24T00:00:00Z" }
]
JSON2. dry-run：出回滚计划（不带 --approved）
npx tsx sdk/apc/bin/apc.ts release rollback --ledger /tmp/apc-rollback-ledger.json --json > /tmp/rb-dry.json; R=$?
echo "rollback(dry) exit=$R"
# 预期：decision=staged (exit 3)，plan.ok=true，plan.from=2.0.7 → plan.to=2.0.63. 审批后执行（带 --approved）—— 真写账本
npx tsx sdk/apc/bin/apc.ts release rollback --ledger /tmp/apc-rollback-ledger.json --approved "$APPROVAL_TOKEN" --json > /tmp/rb.json; R=$?
echo "rollback(apply) exit=$R"
# 预期：decision=green (exit 0)，applied=true；读回 ledger：2.0.7→pulled，2.0.6→current给了 --mirror <bare> 还会把 refs/heads/release-current 重指到 to.tag（git ls-remote 可核）。
4. 负控：无上一好版本 → blocked
echo '[{"version":"2.0.7","tag":"k8s-test-20260724-v2.0.7","status":"current","ts":"2026-07-24T00:00:00Z"}]' > /tmp/rb-single.json
npx tsx sdk/apc/bin/apc.ts release rollback --ledger /tmp/rb-single.json --json; echo "single exit=$?"
# 预期：decision=blocked (exit 1)，plan.ok=false，reason="无上一好版本可回退"Failure / 边界
- 账本无
current/ 无上一好版本 →blocked（真拒，非空转）。 - 本机替身：账本 = 本地 JSON（站位真 release-status 行）；mirror ref = bare 替身；审批 =
--approved非空。真 OTAaction:'rollback'/pulled+ 真 manifest 指针回退 + 服务端 approvalId = M5。 - 回滚后建 bug task 回 bugfix 入口——真 task 创建 = M5 / S10 observability（本 skill 只在
notes提示）。
输出契约（机器判据按这个复算，别自由发挥格式）
本 skill 的判据不是「报告里出现了 pulled / current 这些字」，而是：重解析你贴的三份 --json 产物、从 decision 反推退出码、并把 apply 产物的 plan.next 与磁盘上那份账本文件逐字段深比（json-claim 的 fileEquals + freshArtifacts）。
路径是钉死的（判据要回读它）：
mkdir -p .e2e-tmp/apc-release-rollback
# 三条账本：2.0.5/2.0.6 superseded、2.0.7 current
$EDITOR .e2e-tmp/apc-release-rollback/ledger.json
# 负控用另一份，单条 current
$EDITOR .e2e-tmp/apc-release-rollback/ledger-single.json报告必须带这组行 + 三份原样 JSON（dry-run → apply → 负控）：
RUN-AT: <apply 那次运行的 ISO-8601 墙钟时间>
PLAN-FROM: 2.0.7
PLAN-TO: 2.0.6
STAGED-APPLIED: false
STAGED-EXIT: 3
APPLIED: true
ROLLED-TO: 2.0.6
APPLY-EXIT: 0
NEG-DECISION: blocked
NEG-PLAN-OK: false
NEG-EXIT: 1判据会判红的情况（任一）：
- 没有可解析的 fenced JSON；
- 任一
*-EXIT不是从对应decision推出来的（green→0 · staged→3 · blocked→1）； - dry-run 产物
approved:false却applied:true——审批门被跳； - apply 产物的
plan.next与.e2e-tmp/apc-release-rollback/ledger.json磁盘内容不深等——applied:true而账本没翻，就是宣称了一个没发生的副作用； RUN-AT与那份账本文件的 mtime 差超过 20 分钟——拿上一次 apply 的旧账本冒充这次；- 负控产物不是
plan.ok:false+blocked+applied:false+mirrorRepointed:false+ 有plan.reason——没有上一好版本时必须红，不许空转返绿。
⚠️ 别重复 apply：第 3 步之后再跑一次 apply 会把账本二次翻转，你贴的产物就不再等于磁盘上的账本，判据会红——这不是判据的毛病，是「报告描述的那次写入已经被后一次覆盖」的如实结论。负控必须用另一份
ledger-single.json。
诚实边界：判据能证明「账本现在正是产物声称写成的样子、且写入时间与你声明的运行同期」，不能证明这次写入是 verb 干的而不是你手工 cat > 出来的——没有哪个本地产物是不可伪造的。它杀的是廉价伪造（编计划、叙述已 apply、拿旧账本顶包）。真 release 状态行（服务端账本）落地 = M5。
产出（副作用 oracle，报告里必须给）
- decision + 真退出码：
green/staged/blocked⇄0/3/1。 - 回滚计划：
plan.from.version → plan.to.version（ok:true 时），或plan.reason（ok:false）。 - 账本真副作用（green 时）：读回 ledger 确认
current→pulled、上一好版本→current；不是聊天里说"已回滚"。 - 负控证据：单条账本 →
blocked+plan.ok:false+ reason，证明没东西可回滚时它会红。 - mirror 重指（给了
--mirror）：mirrorRepointed:true+git ls-remote核验release-current指向to.tag。
不许：无上一好版本时硬返绿；把 staged 计划当已回滚；手改 ledger/ref 绕审批。
Show full SKILL.md (229 more words)Show less
Checklist
- dry-run 拿到 plan（from→to）+ staged，再带
--approved执行 - green 后读回 ledger 确认 current→pulled、上一好版本→current
- 跑了单条账本负控，确认 blocked + plan.ok:false（回滚 skill 的命根子）
- 给了
--mirror时用git ls-remote核验 release-current 重指
审批门（doc03 §1）
本 skill 收口 doc03 §1 审批点 「回滚」（release-rollback 执行前）。dry-run 出计划，真回滚前必须建人审批并停手：
出示 dry-run 证据（审批人看到的）：回滚目标版本（
plan.from.version → plan.to.version）+ 影响面（plan.next[]，01 §2）。无上一好版本 →blocked（plan.ok:false），无审批可建。建真 cloud 审批（真路径 =
human-approvalbuilt-in skill 的 CLI）——把上面证据装进请求：bash cloud approval request-human --task-id "$PRISMER_TASK_ID" \ --action "回滚 <plan.from.version> → <plan.to.version>（test）" \ --context "部署后回归红；回滚计划 from→to + 影响面见 dry-run 回执" \ --risk "OTA 账本翻 pulled/current + manifest 指针回退；回滚后建 bug task 回 bugfix 入口"返回
approvalId；建完即停手本轮（human-approval 铁律：平台在人裁决后重派）。block：未 approve 前
staged（exit 3），账本不改；无上一好版本 →blocked（负控注入点，绝不空转返绿）。post-approval = M5 real-remote：真 OTA
action:'rollback'/pulled+ 真 manifest 指针回退 + 服务端校验approvalId，属 M5 real-remote，本机替身（本地 JSON ledger + bare mirror）不触真远端、不冒充已回滚。
PKF 直写（研发回环 · doc07 §B2 写入点①）
产出时机：回滚收口（green/staged/blocked）后，把这次回滚的结论直写成一张 PKF 记忆页（pageType=decision，ReleaseCard 语义 apc/09 §1）——同一页既是回审批人侧的富报告，也是可召回的事故/发版记录。回滚后的事故根因复盘另走 memory skill 的 CONSTRUCT→PLACE→WRITE，两条边并存（doc07 §B1）。这条直写是账本真副作用之外的一次投影。
语法照 pkf-writing skill——本 skill 不再内嵌语法骨架（frontmatter / typed link / 数据块写法都在那边）。写入面不新造：code agent 走 prismer memory write（SS-14 §4.3 appendix；hermes 侧是 native memory_write）。
声明（doc10 §2.5 格式，报告末尾一行）：
PKF: prismer://workspace/<ws>/memory/<path>写入面不可达时如实声明 PKF: none — 写入面不可达（<哪一条>），绝不允许为了满足规则而假装写了。
回读：声明后必须回读该页（pkf_read / memory read），确认真实存在、正文非空且与结论一致（回滚天然带 contradicts——指向被 pulled 版本当初的发版决策页；无上一好版本（blocked）时如实写 plan.ok=false 与 reason，绝不在页里粉饰成"已回滚"）；typed link 的 prismer:// 目标必须真实存在（validator 规则 2c/4 挡 invalid-prismer-host），无对应页就删该 link 行、宁缺勿造伪目标；写入自动挂 INDEX 反孤儿锚（SS-14 §4.2），优先 edit 既有页而非 dump 新叶（PLACE 治理照走）。
<!-- APC-ACK:v1 -->调用回执（APC 平台方运营纪律 · 自动注入，勿手改）
执行本 skill 的第一步，先落一条调用回执：
cloud skill ack release-rollback --task "$PRISMER_TASK_ID"按退出码分流（这条命令的退出码是承重信息，禁止用 || 兜底、; true、
set +e 或重定向把它抹掉）：
| exit | 含义 | 你要做的 |
|---|---|---|
0 | 回执已落库（im_task_logs.action='skill_ack'） | 继续执行本 skill |
3 | 无 task 上下文——本次运行没有 task，产不出回执 | 继续执行本 skill；但本次运行没有回执，任何报告里都不得声称已 ack |
4 | 你不是该 task 的 assignee，服务端拒绝 | 停下并上报：回执只能由执行该 task 的 agent 产生 |
1 | 其它失败（网络 / 服务端） | 重试一次；仍失败则继续执行，并在结果里显式标注「回执缺失」 |
回执只证明本 skill 被调度，不证明执行正确——效果证明由本 skill 自己的 acceptanceCriteria 副作用断言承担（apc/04 §2 层 1 诚实标注）。
<!-- /APC-ACK:v1 -->© Prismer-AI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in sdk/apc/skills/release-rollback of Prismer-AI/PrismerCloud.
- SKILL.md
- skill.json
Open the folder on GitHubat commit e5d9444
Compare with similar skills
Release Rollback next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Rollback this skillPrismer-AI/PrismerCloud | 1.6k | — | ~2.2k | Automated safety check: Notes | MIT | |
| Repo Mirror Sourcesnetdata/netdata | 81k | — | ~1.2k | Automated safety check: Notes | GPL-3.0 | |
| CI Failure Triage and RepairChachamaru127/claude-code-harness | 3.2k | 1 repos | ~1.1k | Automated safety check: Notes | MIT | |
| Bfe Rd Workflowbfenetworks/bfe | 6.3k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Ssh Skillbadseal/ssh-skill | 537 | — | ~2.4k | Automated safety check: Notes | None | |
| GreptimeDB Release RunbookGreptimeTeam/greptimedb | 6.7k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
CI Failure Triage and Repair
Chachamaru127/claude-code-harness
Diagnoses failing CI pipelines and tests, deciding first whether the test or the implementation is at fault, and hands hard cases to a dedicated fixer subagent.
Bfe Rd Workflow
bfenetworks/bfe
引导用户在 bfe 代码库中完成一次完整的功能研发流程，包括需求对齐、文档修改、代码实现、集成测试与回归验证. An agent skill from bfenetworks/bfe.
Ssh Skill
badseal/ssh-skill
A skill your agent uses when a task requires SSH or SCP/SFTP behavior, a remote server, server alias/IP/hostname/user@host, bastion or jump-host access, remote command execution, upload/download…
GreptimeDB Release Runbook
GreptimeTeam/greptimedb
Runbook for publishing a GreptimeDB version: pick the release branch, verify the Cargo version, then tag, create the GitHub release and open the docs note PR.
Crabbox Quickstart
openclaw/crabbox
Gets you running your repository's tests in a disposable Docker or Podman container on your own machine with Crabbox, with no account and no cloud spend.
More from Prismer-AI/PrismerCloud
All 88 skills in this repoPrismer Google Workspace
Prismer-AI/PrismerCloud
Gives an agent account-scoped access to Gmail, Calendar, Drive, Contacts, Docs and Sheets through the gws CLI or a bundled Python client.
Prismer Skill Creator
Prismer-AI/PrismerCloud
Walks an agent through creating, importing, editing, validating, testing and publishing Prismer Skills with a fixed workflow and bundled scripts.
Himalaya Email CLI
Prismer-AI/PrismerCloud
Operates a mailbox from the terminal with the external Himalaya CLI over IMAP, SMTP, Notmuch or Sendmail, separate from any built-in email gateway adapter.
Prismer Image Generation
Prismer-AI/PrismerCloud
Generates one image from a text prompt with a bundled Node.js helper and delivers it once as the attachment to the current Prismer reply.
Manim Explainer Videos
Prismer-AI/PrismerCloud
Produces 3Blue1Brown-style explainer animations with Manim Community Edition for math, algorithms, equations and architecture diagrams, with planning and rendering references.
Prismer Role Builder
Prismer-AI/PrismerCloud
Creates or updates Prismer role templates from a persona, SOP or job description, and turns a role into a working agent that runs its first task through a bundled script.
Related
Works with
Categories
Questions about Release Rollback
What does Release Rollback do?
Roll a release back for real when post-deploy regression goes red — apc release rollback flips the current version to pulled and the last good version back to current in the release ledger, and…. Release Rollback is an agent skill from Prismer-AI/PrismerCloud. Roll a release back for real when post-deploy regression goes red — apc release rollback flips the current version to pulled and the last good version back to current in the release ledger, and (with --mirror) repoints the bare mirror ref.
When should I use Release Rollback?
Release Rollback fits situations like: devOps & Cloud work in your project.
How do I install Release Rollback in Claude Code?
Run `npx skills add Prismer-AI/PrismerCloud --skill release-rollback -a claude-code`. Or copy the skill folder (sdk/apc/skills/release-rollback in Prismer-AI/PrismerCloud) into .claude/skills/release-rollback in your project. Claude Code loads it when a task matches its description.
How do I install Release Rollback in Codex?
Run `npx skills add Prismer-AI/PrismerCloud --skill release-rollback -a codex`. Or copy the skill folder (sdk/apc/skills/release-rollback in Prismer-AI/PrismerCloud) into .agents/skills/release-rollback in your project. Codex loads it when a task matches its description.
Can I use Release Rollback in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Prismer-AI/PrismerCloud --skill release-rollback -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-rollback, .gemini/skills/release-rollback, .github/skills/release-rollback and .opencode/skills/release-rollback in your project.
What does Release Rollback need to run?
Going by SKILL.md and its folder, Release Rollback needs the command-line tools its instructions call (npx and git) and credentials named APPROVAL_TOKEN. Our summary lists: Node.js; A credential in APPROVAL_TOKEN. Its frontmatter pre-approves these tools: Bash. Compatibility (from SKILL.md): ["claude-code"].
Does Release Rollback access the network?
SKILL.md contains no URLs. Its commands use npx and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Release Rollback safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Release Rollback use?
Release Rollback is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release Rollback use?
About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Release Rollback?
Skills that share tags, products or a category with Release Rollback: Repo Mirror Sources (netdata/netdata, 81k stars), CI Failure Triage and Repair (Chachamaru127/claude-code-harness, 3.2k stars), Bfe Rd Workflow (bfenetworks/bfe, 6.3k stars) and Ssh Skill (badseal/ssh-skill, 537 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Rollback?
Prismer-AI (a GitHub organization) maintains it in Prismer-AI/PrismerCloud, which has 1,555 GitHub stars. The repository holds 88 skills in this directory. The repository was last updated on September 30, 2026.
Source: Prismer-AI/PrismerCloud on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.