greptile-tools
Queries indexed repositories via Greptile API for codebase-aware answers. Use when asking natural language questions about code architecture, searching for implementations, understanding how features work, or locating specific code patterns across the repository.
When & Why to Use This Skill
Greptile-tools is a powerful Claude skill that integrates with the Greptile API to provide AI-driven, codebase-aware answers. It enables developers to query their repositories using natural language to understand complex architectures, locate specific code patterns, and gain deep insights into implementation details, significantly enhancing productivity in large-scale software projects.
Use Cases
- Architectural Understanding: Ask high-level questions like 'How does the authentication flow work?' to receive a structural overview of the system design.
- Code Pattern Discovery: Quickly locate specific implementations or recurring code patterns across the entire repository without manual searching.
- Onboarding and Feature Analysis: Help new developers understand how specific features are implemented by providing natural language explanations of the existing code.
- Deep Technical Reasoning: Utilize 'genius mode' for complex analysis, such as tracing intricate logic paths or identifying refactoring opportunities within the codebase.
| name | greptile-tools |
|---|---|
| type | complex |
| depth | base |
| user-invocable | false |
| description | >- |
[H1][GREPTILE-TOOLS]
Dictum: Codebase context enables precise answers.
Query indexed repositories via Greptile API. Defaults to current repo.
[IMPORTANT] Repository must be indexed before querying. Check status first.
# Check indexing status (defaults to current repo)
uv run .claude/skills/greptile-tools/scripts/greptile.py status
# Trigger repository indexing
uv run .claude/skills/greptile-tools/scripts/greptile.py index
# Natural language query
uv run .claude/skills/greptile-tools/scripts/greptile.py query --query "How does authentication work?"
# Deep analysis with genius mode
uv run .claude/skills/greptile-tools/scripts/greptile.py query --query "Explain Effect pipeline patterns" --genius
[1][COMMANDS]
| [INDEX] | [CMD] | [PURPOSE] |
|---|---|---|
| [1] | index |
Trigger repository indexing |
| [2] | status |
Check indexing progress/completion |
| [3] | query |
Natural language codebase Q&A |
[2][OUTPUT]
All commands return {"status": "success|error", ...}. Errors include retryable: bool.
| [INDEX] | [CMD] | [RESPONSE] |
|---|---|---|
| [1] | index |
{status, repo, message} |
| [2] | status |
{status, repo, indexing, sha, progress, ready} |
| [3] | query |
{status, query, answer, sources: [{file, lines}]} |
[2.1][STATUS_FIELDS]
| [INDEX] | [FIELD] | [TYPE] | [PURPOSE] |
|---|---|---|---|
| [1] | status |
str |
"success" or "error" |
| [2] | indexing |
str |
API status: PROCESSING, COMPLETED |
| [3] | ready |
bool |
True when repo is queryable |
| [4] | retryable |
bool |
True for transient errors (on error) |
[3][OPTIONS]
| [INDEX] | [FLAG] | [DEFAULT] | [DESCRIPTION] |
|---|---|---|---|
| [1] | --repo |
bsamiee/parametric_portal |
Repository owner/name |
| [2] | --branch |
main |
Branch to query |
| [3] | --remote |
github |
Remote: github or gitlab |
| [4] | --genius |
false |
Enable deep analysis mode |
| [5] | --query |
— | Natural language query |