← ClaudeAtlas

greptilelisted

Run Greptile CLI for pre-push AI branch review. Use when asked for Greptile review, raycast/extensions pre-PR checks, or as part of the default pre-push review set with coderabbit and lintro-review. Max 2 runs per change set.
lgtm-hq/ai-skills · ★ 0 · Code & Development · score 66
Install: claude install-skill lgtm-hq/ai-skills
# Greptile CLI Review Run **Greptile** (`greptile`) for automated branch review before push. Pair with **`coderabbit`** and **`lintro-review`** for the default pre-push review set — the tools catch different issues and mirror CI. When Greptile (or CodeRabbit) is rate-limited, do not wait for the reset: the `lintro-review` pass is the review of record for that push. ## Relationship to analyze-* skills The `analyze-code`, `analyze-project`, and `analyze-tests` skills are for **manual or agent-driven pre-review checks**—they run concrete commands (lintro, ripgrep, coverage, etc.) and produce structured findings before you open a PR. This skill uses **Greptile CLI** for external AI branch review. Follow the `lint` and `test` skills (or the `commit` skill, which includes them) before invoking Greptile. Do not duplicate full analyze rubrics here. ## Relationship to coderabbit and lintro-review Default pre-push flow when CI runs the review tools: ```text commit → [greptile ‖ coderabbit ‖ lintro-review] → pr ``` Each step names the skill to follow. Run **greptile**, **coderabbit**, and **lintro-review** in parallel (`‖`) when possible. Greptile is typically faster (~1 min). Do not re-run on unchanged code. ## Prerequisites ```bash greptile login greptile whoami ``` Install: `npm i -g greptile` or see [Greptile CLI](https://www.greptile.com/cli). ## Commands - `greptile review -b main --agent` — Review current branch vs main (default for agents) - `greptile review --diff