building-java-knowledge-graph
Analyzes JVM projects (Java/Kotlin/Scala/Groovy) and generates knowledge graphs with tree-sitter parsing. Requires Python 3 on the host and a JVM project with Maven/Gradle/Ant/Ivy build files. Skips gracefully if either prerequisite is missing. Triggers when asked to "build knowledge graph", "analyze project structure", "parse Java codebase", or "generate dependency graph".
- License 许可
- MIT
- 最近更新
- 2026-09-24
- Stars
- ★ 55
- Forks
- 15
01 前言 Front Matter
- name
- building-java-knowledge-graph
- description
- Analyzes JVM projects (Java/Kotlin/Scala/Groovy) and generates knowledge graphs with tree-sitter parsing. Requires Python 3 on the host and a JVM project with Maven/Gradle/Ant/Ivy build files. Skips gracefully if either prerequisite is missing. Triggers when asked to "build knowledge graph", "analyze project structure", "parse Java codebase", or "generate dependency graph".
02 资源文件 5
- 其他.gitignore278 B
- 参考文档references/querying.md2.1 KB
- 参考文档references/schema.md1.3 KB
- 脚本scripts/build_knowledge_graph.py75.1 KB
- 脚本scripts/install_grammars.py2.3 KB
03 SKILL.md 正文
Prerequisites
Step 1 — Verify JVM project:
find "$PROJECT_ROOT" -maxdepth 5 -type f \( -name "*.java" -o -name "*.kt" -o -name "*.scala" -o -name "*.groovy" \) | head -1
If no JVM files found: skip this skill. Set
knowledge_graph_dirtonullinsetup_artifacts. Non-fatal — downstream agents fall back to direct source analysis.
Step 2 — Verify Python:
python3 --version 2>/dev/null || python --version 2>/dev/null
If unavailable: skip this skill with same fallback as above.
Quick Start
# First-time setup (~1 minute)
pip3 install --user 'tree-sitter<0.21'
python3 scripts/install_grammars.py
# Optional: SVG generation
brew install graphviz # macOS
# Analyze project
python3 scripts/build_knowledge_graph.py /path/to/project output-dir
⚠️ DESTRUCTIVE OUTPUT: The script wipes ALL files in output-dir before writing. NEVER point it at a shared directory like {{BASE_PATH}}/ or {{BASE_PATH}}/artifacts/. Use a dedicated subdirectory:
# ✅ SAFE — dedicated subdirectory
python3 scripts/build_knowledge_graph.py /path/to/project {{BASE_PATH}}/artifacts/kg_output
# ❌ DANGER — will delete constitution.md, board.md, other artifacts!
python3 scripts/build_knowledge_graph.py /path/to/project {{BASE_PATH}}
After the script finishes, copy knowledge-graph.json to {{BASE_PATH}}/ for other agents to consume.
What It Detects
- Build systems: Maven (pom.xml), Gradle (build.gradle*), Ant (build.xml), Ivy (ivy.xml)
- Languages: Java, Kotlin, Scala, Groovy via tree-sitter AST
- Structure: Modules, packages, classes, interfaces, enums, annotations
- Relationships: Inheritance, implementations, module dependencies
- Patterns: Architecture layers (controller/service/repository/model/config/util)
- Config:
application*.properties,application*.yaml/yml - Gradle subprojects:
settings.gradleparsing
Output
All outputs are written under the provided artifact path (pass as 2nd argument to the script).
knowledge-graph.json ← complete graph (nodes + edges)
module-dependencies.{dot,svg} ← module dependency diagram
module-{name}.{dot,svg} ← per-module class diagrams
project-{name}.{dot,svg} ← complete project diagram
Resources
references/schema.md— node/edge types, ID patterns, fields, visualization colorsreferences/querying.md— jq and Python query examplesscripts/build_knowledge_graph.py— main analyzerscripts/install_grammars.py— grammar installer
04 同仓库更多 Skills
verify-test-baseline
Generate and run post-migration tests from the frozen baseline specification.
team-request
How team members request infrastructure connection info and handle secrets in team mode
team-charters
Provides role charters (mission, ownership, core principles, quality bar) for a multi-agent coding team. Each charter defines the role's mission, ownership scope, core principle (boundary constraints), and quality bar. Most roles also include communication rules. Consumed by the coordinator during task decomposition to assign work to the correct role. Triggers: "look up role charter", "what does the architect own", "check role boundaries", "find team roles", "which role handles X", "list agent charters", "role responsibilities". NOT for: task decomposition (use breaking-down-tasks), implementation (use implementing-code), architecture analysis (use analyzing-architecture).
struts-to-spring
Migration guideline for transforming Apache Struts 2 applications to Spring Boot 3.x and Spring MVC.
spring-boot-scaffolding
Reference guide for creating a new Spring Boot project during rewrite migration.
sharing-learnings
How to record project learnings so that later-phase workers and future agent runs can consume them.