agentleFS
Sign inStart free
alvinunrealalvinunreal/openpets/.agents/skills/cli-review/SKILL.md

cli-review

Skill1.2k starsChanged 5 months agoMITView 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

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 1 new projectWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 1 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about alvinunreal/openpets

The biggest 5 of 9 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 9

Talked about on GitHub (9 times).

On GitHub · 9

4 more on GitHub
  • Other versions7 projects use a version of this.

    Word for word · 7

    1. alvinunreal/oh-my-opencode-slim★ 10k100% same
    2. alvinunreal/tmuxai★ 2k100% same
    3. OpenPetsHQ/openpets★ 1.4k100% same
    4. greptileai/skills★ 433100% same
    5. alvinunreal/lazyskills★ 252100% same
    6. emngny/oh-my-kilocode-slim★ 9100% same
    7. 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.

  • In this repository2 other files it gives its agents.

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
  1. Distinctive:

    Run a Greptile review from the local checkout and summarize the findings.

    line 16
  2. Distinctive:

    Start from the current repository root:

    line 22
  3. Distinctive:

    If the command fails, tell the user that the Greptile CLI review must be run from a git repository.

    line 28
  4. Very specific:

    Check whether greptile is installed:

    line 32
  5. Distinctive:

    If it is missing, do not install it automatically.

    line 38
  6. Distinctive:

    If npm is unavailable, offer the shell installer fallback:

    line 44
  7. Very specific:

    After installation, re-run command -v greptile.

    line 50
  8. Distinctive:

    Check the signed-in account:

    line 54
  9. Distinctive:

    If the CLI reports that authentication is missing, run:

    line 60
  10. Distinctive:

    Wait for the user to complete the login flow before continuing.

    line 66
  11. Distinctive:

    If JSON output is unsupported or fails with a usage error, fall back to:

    line 76
  12. Distinctive:

    Do not hide the raw command failure if both commands fail.

    line 82
  13. Distinctive:

    When output is plain text, preserve the same structure as much as possible.

    line 94

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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-toplevel

If 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 greptile

If it is missing, do not install it automatically. Ask the user for permission, then show the recommended install command:

npm i -g greptile

If npm is unavailable, offer the shell installer fallback:

curl -fsSL "https://greptile.com/cli/install" | sh

After installation, re-run command -v greptile.

3. Ensure authentication

Check the signed-in account:

greptile whoami

If the CLI reports that authentication is missing, run:

greptile login

Wait for the user to complete the login flow before continuing.

4. Run the review

Prefer JSON output:

greptile review --json

If JSON output is unsupported or fails with a usage error, fall back to:

greptile review --agent

Do 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free