main-branch-update-flow

Updates shared SSoT documents through derived work branches and pull requests.

1|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/Ryokuman/new_human_ochestrator --skill main-branch-update-flow-ryokuman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: main-branch-update-flow
Source: https://github.com/Ryokuman/new_human_ochestrator/tree/main/system/20-skills/main-branch-update-flow
Command: npx skills add https://github.com/Ryokuman/new_human_ochestrator --skill main-branch-update-flow-ryokuman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents unsafe direct edits to the tier-0 main branch by enforcing a controlled workflow where shared rules, AGENTS.md, system docs, prompts, and skill drafts are changed only through derived work branches and reviewed pull requests. ## Core Features & Use Cases - Branch Safety Enforcement: Prohibits direct commits, merges, and rebases on the main branch, requiring all changes to flow through main-v3/{taskname} work branches. - PR Scope Gating: Runs a scope gate before push and PR creation to block project SSoT or local silo data from leaking into tier-0 pull requests. - Codex Review Loop Integration: Coordinates automated PR review cycles with retry, timeout, and issue-classification rules before merge approval. - Use Case: When you need to update shared operating rules or add a new skill draft, this flow creates a work branch, validates the diff scope, opens a Korean-language PR, runs the review loop, and merges only after explicit user approval. ## Quick Start Ask the agent to update the shared system rules or AGENTS.md through the tier-0 update flow and create a pull request for review.

Frequently Asked Questions about main-branch-update-flow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update shared system rules without committing directly to main?

Create a short-lived work branch derived from the tier-0 main branch, make changes only to shared SSoT files, then open a pull request. Direct commits, pushes, and rebases on the main branch are prohibited by this workflow.

How does the PR scope gate work before creating a pull request?

The scope gate checks the branch name, diff paths, and layer classification before push and PR creation. If project SSoT content or local silo data appears in the diff, the PR proposal stops and the content is separated or kept on a project branch.

Can a pull request be merged without explicit user approval?

No. The PR is merged only when the user explicitly states merge intent such as approve, LGTM, or an equivalent phrase. Work approvals like proceed or create the PR are not interpreted as merge approval.

What happens when the Codex review is not configured on the repository?

If Codex review is confirmed missing, unauthorized, or disabled by repo policy, no review pass goal is set and no manual review comment is posted. The skill records the unconfigured status and evidence in the PR body or report.

Why does the workflow forbid rebasing the work branch onto main after merge?

The workflow treats the tier-0 main branch as a merge target only, never as a rebase or fetch baseline for work branches. After a PR merges, the original work branch is not rebased onto main, keeping history aligned with the branch namespace model.