searching-erp-sources

Verifies Neo4j code candidates against local ERP source files and extracts contextual snippets.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Neo4j graph results reflect an older X.12 snapshot of the Divalto ERP and may not match the current X.13 source tree. This Skill confirms which candidate programs still exist on disk, flags disappeared ones, and discovers new relevant code, producing a trustworthy evidence file instead of stale graph data. ## Core Features & Use Cases - Candidate Verification: Glob-searches the ERP tree for each Neo4j candidate program and promotes it to CONFIRME X.13 or DISPARU X.13 status. - Context Extraction: Parses DIVA source structure (Procedure/Function blocks) to return the enclosing block plus a 10-30 line snippet for each match. - Bounded Search & Impact Analysis: Applies strict limits (--max-matches, --max-files, --timeout) across ~7000 files, greps technical keywords for new findings, and detects callers via Call/Execute patterns. - Use Case: After querying the diva-mcp graph for candidates related to a Retail feature request, run the verification workflow to confirm which programs exist in X.13, extract their relevant procedures, and list their callers for an impact study. ## Quick Start Ask the AI to verify the Neo4j candidates in candidates_x12.json against the local ERP source tree and produce an evidence_x13.json report with confirmed, disappeared, and newly discovered programs.

Frequently Asked Questions about searching-erp-sources

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

FAQPage Schema
How do I verify Neo4j code candidates against local ERP sources?

Run verify_x13.py with --candidates pointing to candidates_x12.json, --request to request.json, and --erp-root to the ERP source root. It glob-searches each candidate program and outputs evidence_x13.json with CONFIRME X.13 or DISPARU X.13 statuses.

How to search a large ERP codebase without thousands of grep matches?

Use domain scoping to restrict search to relevant module subdirectories, then apply the built-in bounds: --max-matches 50, --max-files 20, and --timeout 60. The auto scope mode follows the request's domaine_pressenti field and falls back to the full tree if needed.

Does the verification work when Neo4j or diva-mcp is unavailable?

Yes, a direct mode activates when candidates_x12.json has neo4j_status set to unavailable. It ignores the candidate list, searches using only the request's technical and business keywords, and marks all findings as NOUVEAU X.13 with a disclaimer.

Why does the skill use Python instead of ripgrep for searching?

Ripgrep availability is not guaranteed on collaborator machines, and DIVA sources use ISO-8859-1 encoding that needs manual handling for accented characters. Python also reuses the structural DIVA parser for consistent procedure and function detection.

What are the limitations of static impact analysis on DIVA code?

Static text analysis misses dynamic calls like Execute with a variable, Harmony inter-module Ping/Pong tunnels, and framework-resolved hooks. It captures direct Call, Execute with literal names, Module declarations, and HFileVersion table dependencies.