git-review-pipelinelisted

# SDD Review Pipeline Carries the detailed mechanics of the SDD-mode review pipeline. The core `git-workflow.md` rule states the gating contract; this skill carries the execution order, PR-boundary semantics, and branch-protection setup. ## PR-boundary trigger semantics (SDD mode) Review fires only on PRs that target `main` or `master`. PRs into an integration branch (`develop`, `staging`, etc.) are deferred until the integration branch's own PR-to-main opens or syncs - the cumulative review at that point covers everything that landed. | Action | PR base | What fires | |---|---|---| | `gh pr create --base main` | main | code-reviewer + spec-reviewer + doc-updater (full pipeline) | | `gh pr create --base develop` | develop | nothing (deferred) | | `git push` to a branch with open PR -> main | main | full pipeline (PR-sync) | | `git push` to a branch with open PR -> master | master | full pipeline (PR-sync) | | `git push` to a branch with open PR -> develop | develop | nothing (deferred - review fires when develop -> main PR opens or syncs) | | `git push` to a branch with no open PR | - | nothing (deferred until PR opens) | | `git push` to `develop` directly | - | nothing (caught by the develop -> main PR later) | | `git push` to `main`/`master` with no PR | - | nothing (user is expected to have branch protection on; if off, manual verification is on the user) | The cost model shifts from per-push (every commit pair burned a full review) to **per-main-bound PR** (one revie