greptile
Skill1 starsChanged 11 days agoMITView on GitHub
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.
- Installs packages
In this repository41 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- analyze-codeSkill
- analyze-projectSkill
- analyze-testsSkill
- audit-mergesSkill
- babysit-prSkill
- backlogSkill
- branchSkill
- coderabbitSkill
- commitSkill
- implement-issuesSkill
- issueSkill
- jiraSkill
- lintro-addSkill
- lintro-reviewSkill
- lintro-verifySkill
- lintSkill
- properizeSkill
- pr-raycastSkill
- prSkill
- raycastSkill
- rebaseSkill
- reconcileSkill
- scorecardSkill
- stand-ciSkill
- stand-generalSkill
- stand-odinSkill
- stand-pySkill
- stand-rustSkill
- stand-tsSkill
- sweep-prsSkill
- test-apiSkill
- test-shellSkill
- testSkill
- test-ui-qsfSkill
- test-uiSkill
- turbo-addSkill
- turbo-testSkill
- turbo-verifySkill
- which-prSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Run Greptile (greptile) for automated branch review before push.
- Distinctive: line 25
Do not duplicate full analyze rubrics here.
- Distinctive: line 29
Default pre-push flow when CI runs the review tools:
- Very specific: line 37
Run greptile, coderabbit, and lintro-review in parallel (‖) when possible.
- Distinctive: line 66
Run from the repository root on the feature branch
- Distinctive: line 70
When asked to run Greptile or as part of pre-push review:
- Distinctive: line 72
Ensure changes are committed and lint/tests pass
- Very specific: line 73
Run greptile review -b main --agent (can run parallel with CodeRabbit)
- Distinctive: line 75
After fixes to Greptile-sensitive areas, optional verification pass
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
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:
commit → [greptile ‖ coderabbit ‖ lintro-review] → prEach 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
greptile login
greptile whoamiInstall: npm i -g greptile or see Greptile CLI.
Commands
greptile review -b main --agent— Review current branch vs main (default for agents)greptile review --diff— Findings inline with relevant codegreptile review --json— Machine-readable output (use instead of--agentfor parsing)greptile review --resume— Continue the latest unfinished reviewgreptile review show [ID]— Reopen a past review
--agent is an alias for --text (plain text, not JSON). Use --json when a tool
needs structured output.
Rules
- Max 2 Greptile runs per change set (workflow discipline)
- Commit before running — Greptile reviews branch commits vs base; uncommitted changes are ignored
- Default to
-b mainunless the repo uses a different default branch - Run from the repository root on the feature branch
Usage
When asked to run Greptile or as part of pre-push review:
- Ensure changes are committed and lint/tests pass
- Run
greptile review -b main --agent(can run parallel with CodeRabbit) - Analyze findings; address critical/major issues
- After fixes to Greptile-sensitive areas, optional verification pass
- Track run count (max 2 per change set)
For Raycast extension PRs, run static greps from pr-raycast before the CLI review.
Differences from CodeRabbit
| CodeRabbit | Greptile | |
| Scope | all / committed / uncommitted | Branch commits vs base only |
| Agent output | --agent → JSON stream | --agent → plain text; --json for machine-readable |
| Base branch | --base main | -b main |
References
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.

