git-flowlisted

# git-flow — Work Branch and Commit/Push/MR Skill ## Purpose Prepare an updated child branch before implementation, or land an existing non-protected work branch through explicit staging, Korean commit messages, push, and one GitLab merge request. ## Prerequisites Select the requested path before any Git mutation: - Before implementation, read [branch preparation](reference/branch-preparation.md). This path ends after the child branch is ready; it does not load commit, transport, or MR recipes. - To land existing work, read the complete [commit/push/MR contract](reference/kb/operating-contract.md). Keep the current branch; do not run branch preparation over existing changes. Read [principles](reference/principles.md) only for rationale, and [the KB index](reference/kb/INDEX.md) only to find a needed transport or policy topic. They are not unconditional first reads. Both paths preserve Korean user-facing messages, explicit target/default `develop`, existing user changes, and the stop conditions below. ## Instructions 1. Bind the explicit target branch, otherwise `develop`; require a clean, non-diverged base before creating a child branch. 2. For existing work, stop on protected branches, unsafe staged files, missing authority, dirty base preparation, or unresolvable transport. 3. Stage explicit in-scope paths, create coherent Korean commits, check divergence before each push, and create or reuse exactly one MR targeting the bound base. 4. Preserve the contract's tr