deploy-drift-check
仓库创建 2026年7月28日最近提交 7 小时前SkillHot 收录 1 小时前
▸ 精选理由
在调试或发布前快速确认部署漂移,减少误判与重复排查。
这个 Skill 做什么
抓取生产站实际字节与本地提交比对,验证线上是否与预期一致。
直接抓取生产站点的真实字节跟本地提交比对,证明线上到底在跑哪一版,而不是只信 deploy 仪表盘。遇到“应该已经生效但没看到”、准备调试生产或写 postmortem 时用,能迅速确认是不是部署漂移导致的误判。优势是给出可验证的“实际运行”证据,避免为从未上线的代码白忙。
▸ 展开 SKILL.md 英文原文
Prove what is actually running in production matches the commit you think shipped, by fetching real bytes from the live site rather than trusting the deploy dashboard. Use when the user says a fix "should be live", asks why a change is not showing up, is about to debug production, or before writing any postmortem.
0
Stars
0
Forks
20
仓库内 Skill
积累中
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/sriptcollector/toolbay-skills/main/skills/deploy-drift-check/SKILL.md或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/sriptcollector/toolbay-skills/main/skills/deploy-drift-check/SKILL.md"SKILL.MD 节选查看完整文件 ↗
# Deploy Drift Check ## Install Save this file as `~/.claude/skills/deploy-drift-check/SKILL.md`, or `.claude/skills/deploy-drift-check/SKILL.md` to scope it to one repo. Claude Code auto-discovers it. Invoke with `/deploy-drift-check` or by asking "is my latest commit actually live?". ## Why this exists The most expensive class of debugging is investigating code that was never running. Someone reports a bug you fixed last week, you read the fix, the fix is correct, and you spend two hours on a theory that cannot be true because production is serving a build from before it. Dashboards lie by omission here. A deploy marked "Ready" tells you a build succeeded, not that it contains the com
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有