merge-and-deploy
Skill3 starsChanged 8 days agoApache-2.0View on GitHub
当代码改完、要把分支并进远端主干并部署上线时使用:按十五步走完重建组合树、先构建、按改动面选测试套、祖先检查、显式带部署旗标、部署后六样回读与回收工作树,避免带上别人未部署的提交或线上开关被部署脚本静默重置。
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- claude-session-observabilitySkill
- closeout-report-draftingSkill
- context-guard-hooksSkill
- contract-and-test-infraSkill
- doc-pointer-checkSkill
- engineering-pitfalls-checklistSkill
- first-window-requirementsSkill
- frontend-integration-preflightSkill
- hive-dispatchSkill
- legacy-project-onboardingSkill
- memory-index-foldingSkill
- memory-writingSkill
- open-source-preflightSkill
- pointer-handoffSkill
- repo-scale-reportingSkill
- shared-checkout-safetySkill
- short-book-draftingSkill
- subtraction-reviewSkill
- ticket-desk-usageSkill
- top-audit-dispatchSkill
- verify-agent-claimsSkill
- window-handoff-draftingSkill
- zero-window-taskbook-draftingSkill
The file
Files
这个 skill 是干什么的(人话)
代码改完、要合进公共主线并放到线上时,用这个 skill 按固定顺序一步步做。它把合并、构建、测试、推送、部署、上线后核对和收尾排成一条线,每一步都留下能回头核的证据。不用它,容易把别人还没上线的改动一起带上去、把线上开关悄悄冲掉,或者以为上线了其实没生效。
分类
分类:单独装即可用
用前填这几个名字
- {{远端主支}}:正文里说「远端主干」的地方填它,即远端主干分支的完整引用名;例:origin/main
- {{全回归命令}}:正文第 5 步说「全套」「完整套」的地方填它,即跑全量回归测试的命令;例:pytest -q
- {{客户端测试命令}}:正文第 5 步说「客户端套」的地方填它;例:npm test --prefix client
- {{服务端测试命令}}:正文第 5 步说「服务端套」的地方填它;例:pytest server/tests -q
- {{部署构建命令}}:正文第 4 步说「用部署所需构建配置 build 全部工程」的地方填它;例:dotnet build -c Release
- {{线上运行头查看命令}}:正文第 2、9、11 步说「线上头」「从线上读实际运行头」的地方用它读;例:ssh <服务器> cat <部署目录>/REVISION
- {{部署命令}}:正文第 10 步说「部署脚本」的地方填它;例:bash deploy/update.sh
- {{保留线上配置的旗标}}:正文第 10 步说「显式带线上应保留开关的旗标」的地方填它;例:--keep-config
跨窗唤醒
跨窗对话先查工单台,只有对应工单处于执行状态且 ListAgents 显示正在忙的窗口才允许激活对话;空闲超过 30 分钟的视为已完成,不发。已结单不跨会话问,不允许群发;已收口的位只需知会时,在对方工单对话线 say --ref <对方单号> 留一句,不唤醒窗口。查执行态用 $T running(在跑窗口列表)。发送时 to 使用 ListAgents 显示的完整接收名,不用裸短码;接收方非 bypass 时会挂起等待人工批准,超时按未送达处理,不能记成已通知。单独使用时,工单台与窗口列表换成本项目的同类记录和通道。
什么时候用
- 一单改动做完,准备并进远端主干。
- 要把并好的提交部署到线上服务器。
- 同期有别人已推送但还没部署的提交,要先核清再上。
- 部署后要确认线上跑的确实是这次的版本、配置没被冲掉。
- 项目没有线上服务、只并线:照做并线、身份、测试、回收几步,部署相关步骤跳过。
步骤
- 对照「用前填这几个名字」一节,把正文里的对应说法换成你们的实值来理解。
- 读本目录
references/merge-and-deploy.md照做。
正文提到的种子条号、宪法闸号、工单用语和角色名(如 0 号、本位总监、对话线、settle、顶级审计)出自 md-workflow 全套;单独使用时照步骤的意思做,这些引用可跳过或换成你们自己的做法。
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.

