aieos-cross-reference

Validates dependency graphs and detects semantic contradictions across knowledge volumes.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/GuilhermeBrancalhao/ENGINE-CODEX --skill aieos-cross-reference-guilhermebrancalhao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aieos-cross-reference
Source: https://github.com/GuilhermeBrancalhao/ENGINE-CODEX/tree/main/acervo/.claude/skills/aieos-cross-reference
Command: npx skills add https://github.com/GuilhermeBrancalhao/ENGINE-CODEX --skill aieos-cross-reference-guilhermebrancalhao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintaining a multi-volume knowledge base risks broken prerequisite references, dependency cycles, and silent contradictions between volumes that no single author notices. This Skill runs a two-stage audit that catches both structural errors and semantic inconsistencies before they propagate. ## Core Features & Use Cases - Deterministic gate 3 validation: Runs python -m ferramentas.validar --cross-refs to detect nonexistent depende_de ids and cycles in the prerequisite graph, with concrete fix guidance for each violation type. - Semantic contradiction audit: Dispatches the auditor-fable subagent to find duplicated term definitions, conflicting architectural decisions, divergent numeric values, and semantically inverted prerequisites across volumes. - Ordered two-phase workflow: Enforces that the deterministic check passes before the semantic pass runs, preventing analysis of a broken graph. - Use Case: After editing several _VOLUME.yml files in the AI-ENGINEERING-OS collection, run the cross-reference check to confirm no dependency cycles were introduced and that no two volumes now contradict each other. ## Quick Start Ask the assistant to run the cross-reference check on the AI-ENGINEERING-OS collection to validate the dependency graph and audit volumes for contradictions.

Frequently Asked Questions about aieos-cross-reference

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

FAQPage Schema
How do I check cross-references between knowledge base volumes?▼

Run python -m ferramentas.validar --cross-refs from inside the AI-ENGINEERING-OS directory. Exit 0 means the dependency graph is clean; exit 1 lists violations such as nonexistent depende_de ids or cycles, and exit 2 indicates a contract error.

How do I fix a dependency cycle in a prerequisite graph?▼

Identify which of the two edges is merely topical proximity rather than a true reading prerequisite, then remove that edge from the _VOLUME.yml and record the relationship in 18-Referencias-Cruzadas.md instead. Never adjust the validator or test to make the graph pass.

What does depende_de mean in a volume metadata file?▼

depende_de declares a reading prerequisite: an acyclic, directed relation meaning a volume cannot be understood without first reading another. It is not for related or neighboring topics, which belong in a separate cross-references document.

Can a semantic audit run if the deterministic validation fails?▼

No. The semantic pass with the auditor-fable subagent only runs after gate 3 returns exit 0. Running semantic analysis on a broken graph produces findings about the wrong problem, so violations must be fixed first.

Does the cross-reference audit modify the volume files?▼

No. The auditor-fable subagent only reports contradictions with the two files and sentences involved; it never edits volumes. Corrections happen in a separate step, and nothing is written to the auditorias directory in this mode.