greptile
Query, search, and manage repositories indexed by Greptile (AI codebase intelligence)
Setup & Installation
Install command
clawhub install iahmadzain/greptileIf the CLI is not installed:
Install command
npx clawhub@latest install iahmadzain/greptileOr install with OpenClaw CLI:
Install command
openclaw skills install iahmadzain/greptileor paste the repo link into your assistant's chat
Install command
https://github.com/openclaw/skills/tree/main/skills/iahmadzain/greptileWhat This Skill Does
Wraps the Greptile REST API to index, query, and search codebases using AI-powered understanding. Supports GitHub and GitLab repositories, returning answers with source file references or ranked code snippets with line numbers.
Greptile provides AI answers grounded in actual source code with file and line citations, unlike general-purpose LLMs that may hallucinate code structure.
When to Use It
- 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
View original SKILL.md file
# 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 set `GREPTILE_GITHUB_TOKEN`, or authenticate via `gh auth login` — the script falls back to `gh auth token`) ## Commands All commands use `scripts/greptile.sh` (resolve path relative to this skill directory). ### Index a repository ```bash 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 ```bash scripts/greptile.sh status owner/repo [branch] [--remote github|gitlab] ``` Returns: `status` (completed/processing/failed), `filesProcessed`, `numFiles`. ### Query a codebase (AI answer + sources) ```bash 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) ```bash 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 `index` a repo before querying/searching it. Check `status` to confirm indexing is complete. - Use `query --genius` for complex questions (architecture, PR review context, cross-file analysis). - Use `search` when you just need file locations without an AI explanation. - For GitLab repos, pass `--remote gitlab`. - Pipe output through `jq` for formatting: `scripts/greptile.sh query ... | jq .` - Multi-repo queries: not supported by the wrapper; use the API directly with multiple repositories in the body.
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Ask how authentication works in an unfamiliar repo
- 1Ask how authentication works in an unfamiliar repo
- 2Find all files handling payment processing logic
- 3Index a new repo before a code review session
- 4Check whether Greptile has finished processing a large repository
- 5Get file and line references for a specific code pattern
Query, search, and manage repositories indexed by Greptile (AI codebase intelligence)
Security Audits
These signals reflect official OpenClaw status values. A Suspicious status means the skill should be used with extra caution.