GCLI-PULLS-REVIEW(1)

💅 GCLI-PULLS-REVIEW(1) — General Commands Manual 🎀

okay bestie, pull up a chair, we're doing code review on the command line and it's kind of a whole vibe. this is the gcli pulls review page from the General Commands Manual and it's gonna be SO useful i promise.

---

✨ NAME ✨

gcli pulls review — the GCLI Integrated Code Review Tool 🫶

---

✨ SYNOPSIS ✨

gcli pulls review [-o owner -r repo] -i id review

---

✨ DESCRIPTION ✨

⚠️ WARNING! bestie this feature is rather new. expect bugs and broken features, no cap. please report bugs if you hit any!! and honestly the same applies to this manual page — if you spot something mid, please suggest improvements for this feature too. 🥺

to even enable this experimental action you have to do one of these two things:

• set enable-experimental in your gcli config file (peep gcli(5)) to yes, or
• set the environment variable GCLI_ENABLE_EXPERIMENTAL to yes.

either one, your call, slay.

so. the gcli pulls review action lets you do code review tasks on pull requests, on whichever Git forges gcli supports. iconic.

running this action drops you straight into your editor and lets you annotate the diff of the PR. ✍️ here's the tea: comments are always above the change they refer to. a "change" is either a single diff line, or multiple lines wrapped in curly braces on the lines surrounding the change. comments can be prefixed with > like this:

@@ foo.md -0,0 +0,0 @@ hunk starts here
 No change
This is a single line comment
+Foo

> This is is a multiline comment on a multiline diff.
>
> Comment continues here.
{
 not a change
-Removed this line
+Added this line
+Added another line.
}
 this is also not a change

the example up there produces two comments, bestie: the first one refers only to the addition of Foo, and the second one refers to the 4 lines surrounded by the curly braces. obsessed with the curly brace trick honestly. 🎀

and listen — everything leading up to the first diff gets attached as a top-level comment for your review. the way that works is so clean.

after you save and exit the editor, you'll get asked what actions to take on your review. you can:

• request changes 🙅
• approve the changes 👑
• leave a plain comment 💬
• postpone the review locally ⏳

---

✨ OPTIONS ✨

• **-o, --owner _owner** — list PRs in the repository of the given *owner*. this option can **only** be used in combination with -r`. it's giving duo energy, they come as a pair fr fr.
• -r, --repo _repo_ — list PRs in the given repository. this option can only be used in combination with -o. see above, they're literally glued together. 💅
• -i, --id _PR_ — review pull request PR. this is the main character option ngl.

---

✨ EXAMPLES ✨

review PR #69 in the current inferred forge and remote:

$ gcli pulls -i 69 review

review PR #12 in curl/curl on Github:

$ gcli -t github pulls -o curl -r curl -i 12 review

---

✨ SEE ALSO ✨

git(1), git-merge(1), git-branch(1), gcli(1), patch(1)

---

✨ AUTHORS ✨

Nico Sonack aka. herrhotzenplotz <nsonack@herrhotzenplotz.de> and contributors. 🫶 legends only.

---

✨ BUGS ✨

• At the moment the diff cache directory is not created automagically. you have to manually create it in case gcli complains. 😭 (yes really, go make the directory yourself bestie)
• This feature is not implemented (but in active development) on Gitea. 🚧
• Please report bugs at https://sr.ht/~herrhotzenplotz/gcli, via E-Mail to https://lists.sr.ht/~herrhotzenplotz/gcli-discuss or on Github.

---

okay that's the whole page!! 💖 this was gcli 2.13.0, dated 05-Aug-2026 — go review some PRs and slay, bestie. periodt. 🦋✨🌈