greptilelisted

# Greptile CLI Review Run **Greptile** (`greptile`) for automated branch review before push. Pair with **`coderabbit`** for the default pre-CI workflow — both tools catch different issues and mirror CI. ## 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 Default pre-push flow when CI runs both tools: ```text commit → [greptile ‖ coderabbit] → pr ``` Each step names the skill to follow. Run **greptile** and **coderabbit** 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` — Findings inline with relevant code - `greptile review --json` — Machine-readable output (use instead of `--agent` for parsing) - `greptile review --resume` — Continue the latest unfinished review - `greptile review show [