querying-diva-graph

Generates and consolidates Cypher queries against the Neo4j diva-mcp graph to prioritize ERP candidates.

6|Updated May 11, 2026
One-click install
npx skills add https://github.com/divalto/divalto-ia-devkit --skill querying-diva-graph-divalto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: querying-diva-graph
Source: https://github.com/divalto/divalto-ia-devkit/tree/main/plugins/divalto-devkit/skills/querying-diva-graph
Command: npx skills add https://github.com/divalto/divalto-ia-devkit --skill querying-diva-graph-divalto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Exploring the Divalto ERP standard codebase is slow when you don't know which programs, functions, or tables are relevant to a change request. This Skill queries the diva-mcp Neo4j graph (X.12 snapshot) to produce a prioritized candidate list before verification in the live X.13 sources. ## Core Features & Use Cases - Cypher Query Generation: Reads a parsed request.json and selects from 7 parameterized Cypher templates (by keyword, by module, table access, static/dynamic/XMT callers, similar entities) with enforced LIMIT bounds. - Result Consolidation: Deduplicates and scores raw Neo4j rows into a candidates_x12.json file with programs, functions, tables, entities, and call relations, all marked with mandatory X.12 disclaimers. - Graceful Degradation: When the diva-mcp server is unavailable, returns an empty candidate report with neo4j_status unavailable so the X.13 source-search phase can take over. - Use Case: Given a feature request about a Retail payment family (RTFTAB), generate the Cypher queries, execute them via the MCP read tool, and consolidate results into a scored candidate list for verification. ## Quick Start Run the query_neo4j.py script in generate mode with your request.json, execute the returned Cypher via the diva-mcp read tool, then rerun the script in consolidate mode with the raw results.

Frequently Asked Questions about querying-diva-graph

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

FAQPage Schema
How do I query a Neo4j graph to find relevant ERP programs?

Run query_neo4j.py in generate mode with a request.json file. It selects Cypher templates based on detected keywords, module prefixes, table names, and PascalCase function names, then outputs parameterized queries you execute via the diva-mcp read tool.

How do I find all callers of a function including dynamic calls?

Use the three caller templates together: callers_of for static CALLS relations, dynamic_callers_of for DYNAMIC_CALL, and xmt_callers_of for transaction-pattern XMT_CALL invocations. The MCP get_call_graph tool alone misses dynamic and XMT calls.

What happens when the Neo4j MCP server is unavailable?

The skill degrades gracefully: consolidate mode with --neo4j-status unavailable returns an empty candidates_x12.json with neo4j_status unavailable and a disclaimer directing verification to the X.13 source-search phase.

Can I trust Neo4j X.12 snapshot results for X.13 production code?

No. The graph is an X.12 snapshot, so every result carries source diva-mcp-x12 and status X.12 markers plus mandatory disclaimers. All candidates must be verified against X.13 sources by the searching-erp-sources phase before any action.

What are the query limits for Cypher templates in this workflow?

All queries must include LIMIT with N <= 25 for lists and N <= 15 for entity queries, with bounded COLLECT clauses. Queries exceeding 30 seconds are cancelled, and write operations via write_neo4j_cypher are strictly forbidden.