Write visual PR

1. Check the ground

git status --short                       # clean tree?
git remote -v && gh auth status          # remote and auth
git fetch -q origin && git status -sb    # branch pushed and in sync?
gh pr list --state all --json number,headRefName --jq '.[] | select(.headRefName == "<branch>")'   # PR already exists? (old gh has no --head)
git log --oneline <base>..HEAD | wc -l   # commit count
git diff --shortstat <base>...HEAD       # size

• If the remote is on GitLab, use glab for the same checks: glab auth status, glab mr list --source-branch <branch>.
• If neither tool is installed or signed in (common in cloud sessions), use the tools that the environment gives (for example an MCP server) for the same checks and for the creation. Do not stop only because gh or glab is missing.
• If the branch is not on the remote, ask before you push.
• If there is no remote, or the user wants no hosted PR, stop at the body. Report its path and go on with the next step.
• If a PR already exists, update it instead of creating another one.
• Collect real numbers for the description: tests on the base branch and on the branch, commits, files, decisions. Verify each number; do not estimate.