OpenClaw · Skill
Greptile
Query and manage Greptile-indexed repositories via the REST API.
Install
Start with the primary install command. Alternate entrypoints are included below for ClawHub and OpenClaw CLI users.
Primary command
clawhub install iahmadzain/greptileClawHub installer
npx clawhub@latest install iahmadzain/greptileOpenClaw CLI
openclaw skills install iahmadzain/greptileDirect OpenClaw install
openclaw install iahmadzain/greptileWhat this skill does
Query and manage Greptile-indexed repositories via the REST API.
Why it matters
Greptile provides AI answers grounded in actual source code with file and line citations, unlike general-purpose LLMs that may hallucinate code structure.
Typical use cases
- Ask how authentication works in an unfamiliar repo
- Find all files handling payment processing logic
- Index a new repo before a code review session
- Check whether Greptile has finished processing a large repository
- Get file and line references for a specific code pattern
Source instructions
Greptile Skill
Query and manage Greptile-indexed repositories via the REST API.
Setup
Required environment variables:
GREPTILE_TOKEN— Greptile API token (from https://app.greptile.com)GITHUB_TOKEN— GitHub PAT with repo access (alternatively setGREPTILE_GITHUB_TOKEN, or authenticate viagh auth login— the script falls back togh auth token)
Commands
All commands use scripts/greptile.sh (resolve path relative to this skill directory).
Index a repository
scripts/greptile.sh index owner/repo [branch] [--remote github|gitlab] [--no-reload] [--no-notify]
Default branch: main. Use --no-reload to skip re-indexing if already processed.
Check index status
scripts/greptile.sh status owner/repo [branch] [--remote github|gitlab]
Returns: status (completed/processing/failed), filesProcessed, numFiles.
Query a codebase (AI answer + sources)
scripts/greptile.sh query owner/repo [branch] "How does auth work?" [--genius] [--remote github|gitlab]
--genius— slower but smarter analysis (good for PR reviews, architecture questions)- Returns: AI-generated answer + source file references with line numbers
Search a codebase (sources only, no AI answer)
scripts/greptile.sh search owner/repo [branch] "payment processing" [--remote github|gitlab]
Returns: ranked list of relevant files, functions, and snippets with line numbers.
Tips
- Always
indexa repo before querying/searching it. Checkstatusto confirm indexing is complete. - Use
query --geniusfor complex questions (architecture, PR review context, cross-file analysis). - Use
searchwhen you just need file locations without an AI explanation. - For GitLab repos, pass
--remote gitlab. - Pipe output through
jqfor formatting:scripts/greptile.sh query ... | jq . - Multi-repo queries: not supported by the wrapper; use the API directly with multiple repositories in the body.