Open an MR

1. Preflight

New branch, always from the freshly fetched remote: a local target branch may carry unpushed commits that would leak into the MR.

TARGET=$(git symbolic-ref --short refs/remotes/origin/HEAD | sed 's|^origin/||')
git fetch origin "$TARGET"
git checkout -b fix/store-memory-cap "origin/$TARGET"

2. Commits

• One commit per scope (fix(tflint):, feat(module):, chore(live):): two scopes in the diff means two commits, staged by path, never git add -A.
• Before the first push, fold fix-up commits from review rounds into their scope: the MR carries one commit per scope, not the work history.
• Conventional Commits, English, ticket key in the subject or body when there is one. The body says why, wrapped at 72.
• README updated in the same change when a flag, feature or behavior changed.
• Every commit signed: git log --format="%h %G? %s" "origin/$TARGET..HEAD" shows G on each line. Repair unsigned ones with git rebase --exec "git commit --amend --no-edit -S --quiet" "origin/$TARGET", never reset --hard.

3. Push

git fetch origin "$TARGET"
git rebase "origin/$TARGET"
git push --force-with-lease -u origin HEAD

Rebase locally: a server-side rebase (glab mr rebase, the web button) rewrites the commits unsigned.

4. Create

Description in a file so newlines and backticks survive: what, why, test evidence, rollback for infra changes. English, no narrated investigation, no hard wrap. Wording and length rules: ticket-conventions.

glab mr create \
  --target-branch "$TARGET" \
  --title "fix(store): cap memory at 6Gi" \
  --description-file "$BODY" \
  --remove-source-branch \
  --yes

• --yes is mandatory: without it glab waits for a confirmation nobody can send.
• Labels, ticket key placement and any compliance label: whatever the project CLAUDE.md says, applied at creation.
• GitHub: gh pr create --base "$TARGET" --title ... --body-file "$BODY".

5. After

1. echo "<url>" | pbcopy, then answer with the link and one line.
2. New commits on an open MR: push, then rewrite the description to cover them (glab mr update <iid> --description-file "$BODY").
3. Offer the follow-up reminder in one line (tickler) when the change should move performance or cost.