grafema-edge-type-mismatch-debugging

Debug Grafema enrichment failures caused by edge type mismatches.

36|2|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/Disentinel/grafema --skill grafema-edge-type-mismatch-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grafema-edge-type-mismatch-debugging
Source: https://github.com/Disentinel/grafema/tree/main/.claude/skills/grafema-edge-type-mismatch-debugging
Command: npx skills add https://github.com/Disentinel/grafema --skill grafema-edge-type-mismatch-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps debug issues where Grafema enrichment plugins fail to find data due to incorrect edge types being queried, preventing successful code analysis.

Core Features & Use Cases

  • Identify Indexer Output: Determine which edge types are actually created by Grafema indexers (e.g., DEPENDS_ON vs. IMPORTS).
  • Correct Enrichment Queries: Guide users to adjust enrichment plugin logic to match the correct edge types.
  • Direct Graph Querying: Provide methods to directly query the graph database (RFDB) to inspect existing edges and node types.
  • Use Case: When a Grafema plugin reports zero connections found, this skill helps diagnose if the plugin is looking for the wrong type of relationship (edge) in the code graph.

Quick Start

Use the grafema-edge-type-mismatch-debugging skill to find out why enrichment plugins are not finding expected data in the Grafema graph.

Frequently Asked Questions about grafema-edge-type-mismatch-debugging

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

FAQPage Schema
Why does my Grafema enrichment plugin return zero results during code analysis?

Grafema enrichment plugins return zero results when querying incorrect edge types like 'IMPORTS' instead of 'DEPENDS_ON'. This edge type mismatch between indexer output and plugin queries prevents successful code analysis data retrieval.

What is the best way to debug graph edge mismatches in Grafema?

Debugging Grafema graph edge mismatches involves checking indexer configurations to identify actual edge types created, then adjusting enrichment plugin logic to query the correct relationships like 'DEPENDS_ON' instead of 'IMPORTS'.

How do I check which edge types are actually created by Grafema indexers?

Check Grafema indexer configurations to determine which edge types are actually created, such as verifying whether indexers output 'DEPENDS_ON' versus 'IMPORTS' edges, ensuring enrichment plugins query matching relationship types.

Can I directly query RFDB to inspect existing edges and node types?

Yes, you can directly query the RFDB graph database to inspect existing edges and node types, which helps diagnose whether enrichment plugins are looking for the wrong relationship type in the code graph.

How do I fix a Grafema plugin that is looking for the wrong edge type?

Fix Grafema plugins querying wrong edge types by adjusting enrichment plugin logic to match the correct edge types output by indexers, such as updating query parameters from 'IMPORTS' to 'DEPENDS_ON'.

What are the limitations of debugging Grafema edge type mismatches?

Debugging Grafema edge type mismatches is limited to diagnosing enrichment failures caused by incorrect edge type queries like 'IMPORTS' versus 'DEPENDS_ON', requiring access to indexer configurations and direct RFDB querying capabilities.