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:
bash
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
is installed:
If it is missing, do not install it automatically. Ask the user for permission, then show the recommended install command:
If npm is unavailable, offer the shell installer fallback:
bash
curl -fsSL "https://greptile.com/cli/install" | sh
After installation, re-run
.
3. Ensure authentication
Check the signed-in account:
If the CLI reports that authentication is missing, run:
Wait for the user to complete the login flow before continuing.
4. Run the review
Prefer JSON output:
If JSON output is unsupported or fails with a usage error, fall back to:
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.