- name
SKILL.md
技能文件保留在发布者的仓库中。
在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill release-revoke -a cursor -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill release-revoke -a claude-code -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill release-revoke -a codex -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill release-revoke -a grok -y在 Grok Bot 聊天中发送复制的消息。Bot 会从 GitHub 获取这个 SKILL.md,并添加到你所有 Bot 共享的技能中。
Install this skill: https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/HEAD/.pi/skills/release-revoke来自发布者
This skill undoes a release cut by the release-cut skill. It handles
three layers independently because they have different semantics:
Key fact about npm: npm unpublish is blocked 72h after publish, or
any time the version has dependents. The right "revoke" for an npm
release is npm deprecate, which leaves the tarball in place but marks
it with a warning visible to anyone who tries to install it.
Run:
git tag -l 'v*' | sort -V | tail -10
Use AskUserQuestion (select) showing the last 10 tags. Do NOT auto-pick.
Store the chosen version as <version> (with the leading v).
gh release view <version> --json isDraft,publishedAt,assets,url 2>/dev/null || echo "NO_RELEASE"
git tag -l <version> # local tag exists?
git ls-remote --tags origin <version> # remote tag exists?
npm view @blackbelt-technology/pi-dashboard@${version#v} version 2>/dev/null || echo "NOT_ON_NPM"
Parse results and report to the user:
Use AskUserQuestion (confirm) with a full impact preview, e.g.:
About to revoke <version>:
• GitHub Release: PUBLISHED — will be deleted (artifacts gone)
• Git tag: exists locally + on origin — will be deleted from both
• npm: published <N> days ago — will be deprecated
(npm unpublish not possible: > 72h old / has dependents)
This is PARTIALLY REVERSIBLE:
• GitHub Release + tag can be re-created by re-tagging.
• npm deprecation CAN be reversed with `npm deprecate <pkg>@<v> ""`.
• npm version number is burned — cannot republish same version.
Proceed?
Refuse to continue without explicit confirmation.
Only if Step 2 showed the release exists:
gh release delete <version> --yes --cleanup-tag=false
--cleanup-tag=false is important — we delete the tag ourselves in
Step 5 so the ordering is explicit.
git push --delete origin <version> # remote (only if it exists)
git tag --delete <version> # local (only if it exists)
Wrap each in an existence check — don't fail if already gone.
Ask for a deprecation message (AskUserQuestion input), defaulting to:
Deprecated — see https://github.com/BlackBeltTechnology/pi-agent-dashboard/releases for a newer version.
Then run (only if Step 2 confirmed it's on npm):
npm deprecate @blackbelt-technology/pi-dashboard@${version#v} "<message>"
Verify:
npm view @blackbelt-technology/pi-dashboard@${version#v} deprecated
Should echo the message back.
Note: requires the user to be logged in as a maintainer
(npm whoami + having publish rights on the package). If the command
fails with auth error, surface it and ask the user to run
npm login then retry this step.
Check if the latest commit on develop is the release commit:
git log -1 --format="%s" # should be "chore(release): <version>" if yes
If yes, use AskUserQuestion (confirm) to offer:
git revert HEAD --no-edit
git push origin develop
Explain: this restores ## [Unreleased] as the target for the
next release and restores the pre-release package.json versions.
If the release commit is NOT the latest (other commits on top), do not revert automatically — surface the situation and let the user decide. Offer manual guidance:
git revert <sha> + resolve conflictsPrint a final report:
Revocation complete for <version>:
✅ GitHub Release deleted (was: draft|published|absent)
✅ Git tag deleted from origin + local (was: present|absent)
✅ npm deprecated: "<message>" [or: skipped — not on npm]
✅ Release commit reverted [or: skipped — not the latest commit]
Note: the GitHub Pages site still advertises <version> until the next
release (or a manual workflow_dispatch of deploy-site.yml).
npm unpublish without asking. Even within 72h, it breaks
anyone who happens to have installed the broken version. Deprecation
is always the safer default.vX.Y.Z) publish
immediately (not draft) and carry latest*.yml update metadata.
gh release delete removes the release, but electron-updater clients
that already polled /releases/latest may have cached or downloaded
it. Deleting the release stops NEW clients resolving it; it does NOT
recall an update already pulled. To supersede a bad published release,
cut a higher production tag (vX.Y.Z+1) so clients update forward —
do not rely on deletion alone. Pre-release tags stay drafts and have
no such reach.Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on origin, deprecate the npm version (`npm unpublish` is blocked after 72h), and optionally r
---name: release-revokedescription: Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on…---# .pi/skills/release-revoke/SKILL.md概览
Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on origin, deprecate the npm version (`npm unpublish` is blocked after 72h), and optionally revert the release commit. Use when the user says "revoke release", "rollback release", "delete release", "unpublish vX.Y.Z", "yank release".
常见问题
从发布者处下载 .pi/skills/release-revoke/SKILL.md,或复制路径后打开仓库。PlugMCP 只收录该技能,不托管文件。
发布者将它存放在 https://github.com/BlackBeltTechnology/pi-agent-dashboard。
Claude、Cursor、Codex 和 Grok Build 可以读取你从发布者仓库添加的 SKILL.md。在聊天中发送技能的 GitHub 文件夹链接,Grok Bot 就会安装它。