القائمة
Git closure — push the branch and open a PR. The ONLY step that performs git operations. Never auto-merges.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | Closure |
| description | Git closure — push the branch and open a PR. The ONLY step that performs git operations. Never auto-merges. |
| argument-hint | [feature] [--cleanup] |
Closure is the only step that performs git operations. It exists precisely because Accept must do no git. Closure does three things: push the branch, compose a PR description, and open the PR. It never auto-merges — the human merges when ready. Branch cleanup is a separate, optional, post-merge step.
Every pipeline commit carries a subject prefix that matches what the diff actually touches:
brainstorm: / design: / specify: / micro: / northstar: / accept:implement:The prefix must not lie about the diff. A spec-only prefix on a commit that also changed source code is a labeling mismatch — fix it with git commit --amend or a rebase, never force past it. You can enforce this with an optional git pre-commit hook (see docs/extending.md), but the discipline stands on its own.
Read project-state.md (active feature, mode) and approvals/master.json to detect which closure this is:
review record yet. PR targets the feature branch. Title: {feature} G{N} — {group title}.review record exists. PR targets main. Title: {feature-name}.{NNN}-{feature-name}) and that there are commits to push.git push -u origin {branch-name} (skip with a note if already up to date).git diff --stat.gh pr create --title "{title}" --body "{body}" --base {target} — base is the feature branch for group closure, main for feature closure. Never auto-merge.--cleanup, post-merge only): verify the PR is merged (refuse if not), then git checkout main && git pull, git branch -d {branch}, git push origin --delete {branch}. Idempotent.main.- "close this out"
- "push and open a PR"
- "ship the group"
- "create the pull request"
The drift check. Compare what was built against the design doc and master spec. Sets the Double Gate — A3 cannot start until A1 is at zero findings.
Mechanical FR/AC compliance. Walk every functional requirement and acceptance criterion and render a binary Pass/Fail with evidence. No judgment about quality, direction, or architecture.
Code/content quality. Dead code, hardcoded values, leftover TODOs, weak error handling, security holes, performance traps, standards violations. Enforces the Double Gate — blocks until A1 is at zero findings.
Vision-gap analysis. Compared to the perfect-world North Star, what is missing, drifting, or underbuilt — and what to add or change now to close the gap. Not a passive alignment scorecard.
Research the world. Real web research to find what the best teams do for every technology and pattern in the build, then implement superior approaches now (not later). The only lens that brings outside knowledge.
The boundary ritual — review what just landed, record an approval, journal it, and advance the phase. The ONLY step that writes approvals, and it does NO git.