Individual skill
repopedia
Use when working with a codebase's structure — finding who calls a function, what breaks if code changes (blast radius), looking up symbols, or generating code documentation. For Python/TypeScript repos indexed into a repopedia knowledge graph.
SKILL.md
Source commit 5fe2c92a1efd3e7ba624b16b4735a0e6c39cb060
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 16
- Repository last updated
- Oct 3, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- code-analysis Repository topic
- developer-tools Repository topic
- documentation Repository topic
- knowledge-graph Repository topic
- mcp Repository topic
- python Repository topic
- static-analysis Repository topic
- tree-sitter Repository topic
- agent-skills Repository topic
- claude-skill Repository topic
- docs Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
.github/workflows/ci.ymlasset · 390 bytes.gitignoreasset · 172 bytesLICENSEasset · 1,067 bytesREADME.mddoc · 14,501 bytesREADME_ZH.mddoc · 13,550 bytesSKILL.mdcore · 3,637 bytesSKILL.mdcore · 3,637 bytesSKILL.mdcore · 3,637 bytesSKILL.mdcore · 3,637 bytesdist/repopedia-0.1.0-py3-none-any.whlasset · 39,873 bytesdist/repopedia-0.1.0.tar.gzasset · 44,719 bytesdocs/assets/architecture-hero.svgasset · 196,164 bytesdocs/assets/requests-inheritance.svgasset · 257,378 bytesdocs/gallery.mddoc · 3,972 bytespyproject.tomlasset · 872 bytesrepopedia.egg-info/PKG-INFOasset · 14,524 bytesrepopedia.egg-info/SOURCES.txtdoc · 694 bytesrepopedia.egg-info/dependency_links.txtdoc · 1 bytesrepopedia.egg-info/entry_points.txtdoc · 49 bytesrepopedia.egg-info/requires.txtdoc · 109 bytesrepopedia.egg-info/top_level.txtdoc · 10 bytesrepopedia/__init__.pyruns · 48 bytesrepopedia/__main__.pyruns · 125 bytesrepopedia/cli.pyruns · 9,334 bytesrepopedia/extract/__init__.pyruns · 671 bytesrepopedia/extract/base.pyruns · 3,498 bytesrepopedia/extract/python.pyruns · 7,283 bytesrepopedia/extract/typescript.pyruns · 6,828 bytesrepopedia/incremental.pyruns · 7,883 bytesrepopedia/index.pyruns · 11,822 bytesrepopedia/llm.pyruns · 3,733 bytesrepopedia/mcp_server.pyruns · 6,544 bytesrepopedia/query.pyruns · 5,871 bytesrepopedia/search.pyruns · 4,330 bytesrepopedia/store.pyruns · 11,185 bytesrepopedia/wiki.pyruns · 14,651 bytestests/__init__.pyruns · 0 bytestests/fixtures/pyrepo/pkg/__init__.pyruns · 0 bytestests/fixtures/pyrepo/pkg/broken.pyruns · 22 bytestests/fixtures/pyrepo/pkg/core.pyruns · 327 bytestests/fixtures/pyrepo/pkg/util.pyruns · 110 bytestests/fixtures/tsrepo/src/broken.tsruns · 20 bytestests/fixtures/tsrepo/src/service.tsruns · 413 bytestests/fixtures/tsrepo/src/util.tsruns · 143 bytestests/test_incremental.pyruns · 5,225 bytestests/test_index.pyruns · 8,603 bytestests/test_mcp.pyruns · 3,906 bytestests/test_query.pyruns · 4,002 bytestests/test_search.pyruns · 2,516 bytestests/test_wiki.pyruns · 4,149 bytes
Read excerpt
# repopedia
repopedia builds a **code knowledge graph** from a source repo (tree-sitter AST → SQLite): symbols, calls, imports, inheritance. Query it structurally instead of guessing from text search. Every answer cites `file:line`. MIT-licensed, local-first, no Docker, no server.
## When to use repopedia vs alternatives
| Question | Best tool |
|---|---|
| "Who calls `Engine.run`?" / "What breaks if I change this?" | **repopedia** (`get_callers`, `blast_radius`) — needs the call graph, text search can't do this |
| "Where is the retry logic?" (keyword-ish) | **repopedia** (`search_codebase`: BM25 + one graph hop) or ripgrep for exact strings |
| "What does this function do?" (semantics) | vector RAG / LLM reading the file — repopedia gives structure, not meaning |
| Multi-hop: "who mentors the engineer leading Project Phoenix?" | **repopedia** — joins across files via graph traversal |
Rule of thumb: **structure questions → repopedia; meaning questions → LLM; exact strings → ripgrep.**