cli-review
Skill2k starsChanged 5 months agoApache-2.0View on GitHub
Runs a Greptile CLI review for the current local branch, installing or authenticating the CLI when needed, then summarizes JSON findings for the user. Use when the user wants Greptile feedback before opening a PR, outside a hosted PR review flow, or directly from a local checkout.
- Pipes a download into a shell
- Installs packages
7 other projects use a version of this; 1 new project in the last 4 weeks, against 0 the 4 before.
Adopted by
Surging: 1 new project took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- emngny/oh-my-kilocode-slimword for word, first seen Nov 8, 2026
- kellykampen/agent-skillsword for word, first seen Nov 1, 2026
- greptileai/skillsword for word, first seen Oct 25, 2026
- alvinunreal/oh-my-opencode-slimword for word, first seen Oct 8, 2026
- alvinunreal/openpetsword for word, first seen Jun 30, 2026
- OpenPetsHQ/openpetsword for word, first seen Jun 30, 2026
Who's talking about alvinunreal/tmuxai
- @matsuu.bsky.social“tmuxのsession内で動作するAIアシスタント。画面を3分割して1つのpaneをチャット用にすると。なるほどtmux活用してる。homebrewでインストール可”Bluesky · May 3, 2025 · 7 likes
- @tom-doerr.bsky.social“https://github.com/alvinunreal/tmuxai”Bluesky · Aug 30, 2025 · 1 likes
- @technews4869.bsky.social“github.com/alvinunreal/tmuxa... GitHub - alvinunreal/tmuxai: AI-Powered, Non-Intrusive Terminal Assistant”Bluesky · May 4, 2025 · 1 likes
- @yug1224.com“Tmux上の作業内容をAIが常に把握して、文脈に合った助言やコマンド実行を手伝うっぽい。ターミナル作業を中断せずにAIの助けを借りたい時に便利かも。 yug1224 starred alvinunreal/tmuxai…”Bluesky · May 4, 2025 · 1 likes
- NixOS/nixpkgs“tmuxai: 2.4.0 -> 2.5.0”GitHub · Nov 1, 2026
The biggest 5 of 43 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 43
Talked about on GitHub and Bluesky (43 times).
On GitHub · 39
- Nov 1, 2026tmuxai: 2.4.0 -> 2.5.0 — NixOS/nixpkgs0 reactions · 2 comments
- Oct 30, 2026tmuxai 2.5.0 — Homebrew/homebrew-core0 reactions · 1 comment
- Oct 8, 2026tmuxai: 2.3.2 -> 2.4.0 — NixOS/nixpkgs0 reactions
- Sep 28, 2026tmuxai 2.4.0 — Homebrew/homebrew-core0 reactions · 1 comment
- Sep 7, 2026tmuxai: 2.3.1 -> 2.3.2 — NixOS/nixpkgs0 reactions · 2 comments
34 more on GitHub
- Sep 7, 2026tmuxai 2.3.2 — Homebrew/homebrew-core0 reactions · 1 comment
- Jul 13, 2026tmuxai: 2.2.2 -> 2.3.1 — NixOS/nixpkgs0 reactions
- Jul 7, 2026tmuxai 2.3.1 — Homebrew/homebrew-core0 reactions · 1 comment
- Jul 1, 2026tmuxai 2.3.0 — Homebrew/homebrew-core0 reactions · 1 comment
- May 21, 2026tmuxai: 2.2.1 -> 2.2.2 — NixOS/nixpkgs0 reactions · 2 comments
- May 18, 2026Align module identity with `github.com/ap0ught/tmuxai` to unblock `go install ...@main` — ap0ught/tmuxai0 reactions
- May 18, 2026Make Windows builds compile by isolating Unix-only process and polling code paths — ap0ught/tmuxai0 reactions · 2 comments
- May 14, 2026tmuxai 2.2.2 — Homebrew/homebrew-core0 reactions · 1 comment
- May 7, 2026tmuxai 2.2.1 — Homebrew/homebrew-core0 reactions · 1 comment
- May 1, 2026tmuxai 2.1.4 — Homebrew/homebrew-core0 reactions · 1 comment
- Mar 23, 2026tmuxai: 2.1.1 -> 2.2.1 — NixOS/nixpkgs0 reactions · 4 comments
- Mar 18, 2026tmuxai 2.1.2 — Homebrew/homebrew-core0 reactions · 1 comment
- Mar 14, 2026tmuxai: 2.0.2 -> 2.1.1 — NixOS/nixpkgs0 reactions · 2 comments
- Mar 14, 2026tmuxai 2.1.1 — Homebrew/homebrew-core0 reactions · 1 comment
- Feb 12, 2026Fix tmuxai download to use correct repository and tar.gz release format — zeddius1983/unraid-tmuxai0 reactions · 1 comment
- Nov 11, 2025tmuxai: 2.0.1 -> 2.0.2 — NixOS/nixpkgs0 reactions · 2 comments
- Nov 7, 2025tmuxai 2.0.2 — Homebrew/homebrew-core0 reactions · 1 comment
- Oct 29, 2025Bump mise from v2025.10.18 to v2025.10.19 — carapace-sh/scrape0 reactions
- Oct 28, 2025tmuxai: 2.0.0 -> 2.0.1 — NixOS/nixpkgs0 reactions
- Oct 27, 2025fix(alvinunreal/tmuxai): windows builds were removed at ttmuxai v2.0.1 — aquaproj/aqua-registry0 reactions
- Oct 27, 2025tmuxai 2.0.1 — Homebrew/homebrew-core0 reactions · 1 comment
- Oct 27, 2025chore: update alvinunreal/tmuxai v2.0.0 to v2.0.1 — aquaproj/aqua-registry0 reactions · 1 comment
- Oct 22, 2025tmuxai: 1.1.3 -> 2.0.0 — NixOS/nixpkgs0 reactions · 3 comments
- Oct 18, 2025tmuxai 2.0.0 — Homebrew/homebrew-core0 reactions · 1 comment
- Oct 16, 2025tmuxai: 1.1.2 -> 1.1.3 — NixOS/nixpkgs0 reactions · 2 comments
- Oct 12, 2025tmuxai 1.1.3 — Homebrew/homebrew-core0 reactions · 1 comment
- Oct 9, 2025tmuxai: 1.1.1 -> 1.1.2 — NixOS/nixpkgs0 reactions · 2 comments
- Oct 3, 2025tmuxai 1.1.2 — Homebrew/homebrew-core0 reactions · 1 comment
- Sep 19, 2025tmuxai: init at 1.1.1 — NixOS/nixpkgs0 reactions · 5 comments
- Aug 20, 2025Suggestion: add tmuxai to the list — rothgar/awesome-tmux0 reactions
- Aug 16, 2025tmuxai 1.1.1 — Homebrew/homebrew-core0 reactions · 1 comment
- Jun 2, 2025tmuxai 1.1.0 — Homebrew/homebrew-core0 reactions · 1 comment
- May 30, 2025tmuxai 1.0.4 — Homebrew/homebrew-core0 reactions · 1 comment
- May 11, 2025Add github.com/alvinunreal/tmuxai — aquaproj/aqua-registry0 reactions · 2 comments
On Bluesky · 4
- May 3, 2025tmuxのsession内で動作するAIアシスタント。画面を3分割して1つのpaneをチャット用にすると。なるほどtmux活用してる。homebrewでインストール可 — @matsuu.bsky.social7 likes and reposts
- Aug 30, 2025https://github.com/alvinunreal/tmuxai — @tom-doerr.bsky.social1 likes and repost
- May 4, 2025github.com/alvinunreal/tmuxa... GitHub - alvinunreal/tmuxai: AI-Powered, Non-Intrusive Terminal Assistant — @technews4869.bsky.social1 likes and repost
- May 4, 2025Tmux上の作業内容をAIが常に把握して、文脈に合った助言やコマンド実行を手伝うっぽい。ターミナル作業を中断せずにAIの助けを借りたい時に便利かも。 yug1224 starred alvinunreal/tmuxai… — @yug1224.com1 likes and repost
Other versions7 projects use a version of this.
Word for word · 7
- alvinunreal/oh-my-opencode-slim★ 10k100% same
- OpenPetsHQ/openpets★ 1.4k100% same
- alvinunreal/openpets★ 1.2k100% same
- greptileai/skills★ 433100% same
- alvinunreal/lazyskills★ 252100% same
- emngny/oh-my-kilocode-slim★ 9100% same
- kellykampen/agent-skills★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 11 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Run a Greptile review from the local checkout and summarize the findings.
- Distinctive: line 22
Start from the current repository root:
- Distinctive: line 28
If the command fails, tell the user that the Greptile CLI review must be run from a git repository.
- Very specific: line 32
Check whether greptile is installed:
- Distinctive: line 38
If it is missing, do not install it automatically.
- Distinctive: line 44
If npm is unavailable, offer the shell installer fallback:
- Very specific: line 50
After installation, re-run command -v greptile.
- Distinctive: line 54
Check the signed-in account:
- Distinctive: line 60
If the CLI reports that authentication is missing, run:
- Distinctive: line 66
Wait for the user to complete the login flow before continuing.
- Distinctive: line 76
If JSON output is unsupported or fails with a usage error, fall back to:
- Distinctive: line 82
Do not hide the raw command failure if both commands fail.
- Distinctive: line 94
When output is plain text, preserve the same structure as much as possible.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CLI Review
Run a Greptile review from the local checkout and summarize the findings.
Instructions
1. Confirm repository context
Start from the current repository root:
git rev-parse --show-toplevelIf the command fails, tell the user that the Greptile CLI review must be run from a git repository.
2. Check for the Greptile CLI
Check whether greptile is installed:
command -v greptileIf it is missing, do not install it automatically. Ask the user for permission, then show the recommended install command:
npm i -g greptileIf npm is unavailable, offer the shell installer fallback:
curl -fsSL "https://greptile.com/cli/install" | shAfter installation, re-run command -v greptile.
3. Ensure authentication
Check the signed-in account:
greptile whoamiIf the CLI reports that authentication is missing, run:
greptile loginWait for the user to complete the login flow before continuing.
4. Run the review
Prefer JSON output:
greptile review --jsonIf JSON output is unsupported or fails with a usage error, fall back to:
greptile review --agentDo not hide the raw command failure if both commands fail. Summarize the failing command and the next action the user needs to take.
5. Summarize results
Parse JSON output when available and report:
- Review status
- Number of findings
- Highest severity findings first
- Files that need edits
- Suggested next command or fix path
When output is plain text, preserve the same structure as much as possible. Keep the summary concise and focused on actionable findings.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

