git-opslisted

The umbrella for devloop's git + code-review workflow. All git goes through one runner (`lib/gitcmd.py`); all code-review hosting through one facade (`lib/forge/`), which picks GitHub or GitLab per-repo from the origin remote. You call the scripts below — never raw `git commit/push` (the guards intercept those, and the scripts encode the case logic + self-narrate a `PLAN:` banner you can trust), and **never hand-roll `curl`/`glab`/`gh` against the forge API** — that one facade backs both script surfaces below (gcampr *raises* an MR; `pr` *inspects/manages* an existing one) and resolves the token from config, so there's no credentials file to hunt for. Paths use `<PLUGIN_ROOT>` → `${CLAUDE_PLUGIN_ROOT}` on Claude Code; `${PLUGIN_ROOT}` on Codex. ## Operating principles The scripts are the executable policy; this skill supplies the decision model. Inspect Git state freely, but do not improvise a competing mutation sequence when devloop owns that operation. 1. **Resolve intent before touching HEAD.** `--branch` means new work and cuts from a freshly fetched `origin/<target>`; omitting it means continue the current branch. Stacking is never inferred from the current checkout — it requires an explicit `--base`. 2. **Treat an existing identity as work to preserve.** Reusing a branch or worktree tag means resume it as-is, not “make it current.” Checkout must not silently rebase or reset existing work. Updating its baseline is a separate, explicit history operation. 3