mcpField
S
stacked-delivery

stacked-delivery

github.com/yeachan-heo其他40.7k8 次安装今天更新
代码仓库

关于 stacked-delivery

用于将相互依赖的变更作为一串关联 PR 交付的工作流技能。它按补丁 ID 跟踪验证结果，变基后要求重新验证，并将合并权保留给人。

主要功能

  1. 01为每项变更创建分支和关联 PR
  2. 02逐层构建并验证堆栈
  3. 03按补丁 ID 跟踪验证结论
  4. 04变基后使过期结论失效
  5. 05由人自底向上合并各层
  6. 06报告链路状态和验证情况

适用场景

  1. 01交付依赖前序 PR 的变更
  2. 02管理需要按顺序合并的评审工作
  3. 03检查堆栈中哪些层需要重新验证

安装

复制下面的命令，在终端中运行。

$npx skills add https://github.com/yeachan-heo/oh-my-claudecode --skill stacked-delivery

安装后在 Claude Code 中输入/stacked-delivery确认已加载。

README 原文English

来自项目 README

README 暂无中文译文，以下为英文原文；中文介绍见上方。

Stacked Delivery

Some queues cannot merge independently — each change depends on the last — so they ship as one stacked chain: PR 2 branches on PR 1, PR 3 on PR 2. The chain makes review sequential and landing strictly bottom-up; this skill keeps that honest.

When to use

  • changes depend on each other and the user chose stacking over independent PRs
  • review gating means only the bottom PR can actually merge at a time

When not to use

  • changes are independent — parallel PRs merge faster and fail smaller
  • the user wants everything in one PR — that is execute with a bigger brief

Workflow

  1. Cut the stack: one branch and PR per change, each branched on the last; the brief for each PR comes from sharpen/architect as usual. Every PR description links its parent and child.
  2. Build and verify each layer with its own checks — a red middle PR blocks the whole chain, so fix forward before adding layers on top.
  3. Record patch-ids: verification verdicts (from verify) record the head SHA they were earned on, in .omc/state/verification-ledger.tsv — the ledger's sha field. A verdict applies only to that exact patch. Review verdicts (interrogate pass/revise/block) are tracked in the PR's review thread, not the verification ledger — the ledger's vocabulary is verification evidence, and review outcomes have their own lane.
  4. On rebase: any PR whose base moved has its verdicts invalidated for the affected layers — re-run the checks and record fresh verdicts before the chain is "green" again. A stale green is the stack's most dangerous lie.
  5. Land bottom-up only: the human merges PR 1; the stack rebases onto the new trunk; re-verify; PR 2 becomes the new bottom. This skill never merges — landing authority stays with the human (babysit rules apply).
  6. Report: the chain shape (PR list with parent links), each layer's verdict and patch-id, and which layers are re-verified against the current trunk.

Rules

  • Never merge, rebase, or force-push shared branches on your own; rebase of own-branch layers uses --force-with-lease and says so.
  • Never present a layer as green whose base moved after its verdict was earned — the ledger's patch-id is the truth.
  • A failing layer stops the chain at that layer; layers above are blocked-and-waiting, not green.

评论

支持 Markdown