Description
Repository Knowledge Graph turns a local codebase into connected Dots knowledge and keeps that map useful over time. It ingests repository files and symbols, checks graph freshness, and can enrich the structural spine with semantic edges to specifications, Tasks, artifacts, and features. Agents can then answer impact and provenance questions from shared graph state rather than repeatedly rediscovering the tree.
The workflow separates deterministic ingest from judgment-heavy enrichment. Ingest establishes the repository spine; enrichment reads both endpoints, uses a controlled edge vocabulary, and verifies every write. The plugin skill is the shared operational face over the Dots repo-graph platform, with explicit age checks so stale graph data is never presented as current.
Selling Points
- Makes code structure queryable by every connected agent, not just the session that inspected it.
- Connects implementation to specifications and work records, preserving why code exists.
- Detects staleness before graph-backed answers, reducing confident conclusions from old snapshots.
- Uses controlled, reasoned edges that remain explainable during later traversal.
- Avoids repeated whole-repository exploration by sharing one durable code map.
User Story
A maintainer asks which files and symbols implement a particular specification. The workflow checks that the repository graph matches the current checkout, refreshes it if needed, and traverses the semantic edges from the spec to code. The maintainer receives cited paths and can inspect impact without manually searching every package.
Extension Surface
This shared feature is automatable. payload/skills/repo-graph/SKILL.md exposes ingest and enrichment routes, while payload/skills/repo-graph/scripts/ingest-repo.mjs drives repeatable graph creation. The vocabulary and edge rules live in payload/skills/repo-graph/workflows/enrich-graph.md. Consumers can invoke and query the lifecycle, but cannot plug in arbitrary parsers or edge vocabularies through this skill.
Capabilities & Limits
- Ingests repository files and symbols into a durable graph and detects changes against the live checkout.
- Enriches structural data with reasoned links to specs, Tasks, artifacts, and other knowledge.
- Supports graph-first caller, impact, provenance, and context questions.
- Limit: stale graphs must be refreshed; ambiguous endpoints are not guessed, and cross-repository relationships require explicit supported handling.
Implementation Map
payload/skills/repo-graph/SKILL.mdpayload/skills/repo-graph/workflows/ingest-repo.mdpayload/skills/repo-graph/workflows/enrich-graph.mdpayload/skills/repo-graph/scripts/ingest-repo.mjspayload/skills/repo-graph/references/graph-first.md