rc-git

Git Branch, Push & PR

Take the work currently in this repo from "changes on disk" to "PR opened", stopping for the user's confirmation at every outward-facing step. This skill is standalone — it does not read or require any .rc/ workflow artifacts.

Ask every confirmation question in the user's language. An optional Linear issue (e.g. PROJ-123) may be supplied when the skill is invoked; if present, use it and skip the ticket question.

Always write the PR title and description in Brazilian Portuguese (pt-BR), regardless of the conversation language. Keep the conventional-commit type prefix (feat:, fix:, etc.) in the title; everything else is in pt-BR.

Use a TodoWrite list to track the phases. Run them in order; commit, push, and opening the PR each need their own explicit yes — approval for one step never carries over to the next.

Phase 0 — Gather git state

Before anything else, inspect the real repository state by running:

git rev-parse --is-inside-work-tree           # is this a git repo?
git branch --show-current                      # current branch (empty = detached HEAD)
git symbolic-ref --quiet refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@'  # default branch
git status --short                             # working tree changes
git log --oneline @{u}..HEAD                   # local commits ahead of upstream
git remote -v                                  # remotes
command -v gh                                  # is the gh CLI available?

Base every later decision on this real state, not on assumptions.

Phase 1 — Inspect & guard

• If this is not a git repo → stop and say so. Don't run anything else.
• If HEAD is detached → stop and ask the user to check out a branch first.
• Determine the default branch (the remote HEAD from Phase 0; if unknown, ask the user — commonly main or master).
• If the working tree is clean and there are no local commits ahead of the upstream/default → there's nothing to ship: tell the user and stop.