repoql

Build a local knowledge graph of repository structure for semantic code exploration.

9|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/stueeey/RepoQL.Public --skill repoql
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repoql
Source: https://github.com/stueeey/RepoQL.Public/tree/main/clawdbot/skills/repoql
Command: npx skills add https://github.com/stueeey/RepoQL.Public --skill repoql

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

RepoQL provides a local knowledge graph for repositories, allowing teams to explore code structure and relationships without reading every file.

Core Features & Use Cases

  • Inventory: quickly understand what exists in a codebase.
  • Locate: find where a symbol or file is implemented.
  • Inspect: view structure and relationships with contextual snippets.
  • Explain: synthesize how components interact and answer architectural questions.

Quick Start

Inspect a repository by inventorying its structure and then locating key concepts with targeted queries.

Frequently Asked Questions about repoql

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I explore an unfamiliar codebase without reading every file?

To explore an unfamiliar codebase without reading every file, you can build a local knowledge graph of the repository structure. This approach indexes code relationships to enable semantic searches and targeted pattern discovery.

What is the best way to locate where a specific symbol is implemented in a large repository?

The best way to locate where a symbol is implemented in a large repository is using semantic search within a local knowledge graph. This allows you to pinpoint specific files and inspect their structural relationships quickly.

How does building a knowledge graph help with code exploration and architecture inspection?

Building a knowledge graph helps with code exploration by indexing repository structure into a navigable format. This enables you to inventory components, locate implementations, and inspect architectural relationships without manual file traversal.

Can I perform semantic searches to discover code patterns across an entire project?

Yes, you can perform semantic searches to discover code patterns across an entire project. By indexing the code structure into a knowledge graph, you can query complex architectural relationships and synthesize component interactions.

Does this code exploration approach work for understanding component interactions in unfamiliar codebases?

Yes, this code exploration approach works for understanding component interactions in unfamiliar codebases. It supports an explain workflow that synthesizes how different parts of the architecture interact based on the indexed knowledge graph.

What are the limitations of using a local knowledge graph for repository code exploration?

A limitation of using a local knowledge graph for repository code exploration is that it requires indexing code structure first. This approach focuses on structural and semantic queries rather than providing a direct runtime execution trace.