git-flow
Git Flow
Resolve the repository context first
Read repository instructions, git status --short --branch, git remote -v, git branch -a, and recent commit/merge history before choosing a branch or command. Fetch the relevant remote refs before comparing them.
Resolve source, base, target, and naming in this order: explicit user instruction → repository instructions → verified remote/MR/PR context → the conventions below. A default branch alone does not prove the intended merge target. Ask one focused question only if remaining ambiguity changes the result.
These tables describe MEDcury conventions, not every repository. For other repositories, use their verified conventions. Preserve an existing task branch and unrelated staged/unstaged work; use an isolated worktree when switching would disturb it. If no ticket was supplied, use the repository's descriptive branch convention without inventing a ticket ID.
Before mutation, state the selected base, working branch, and intended target. Continue within authorization already given; creating a branch or committing does not itself authorize pushing, publishing a release, or merging.