eightforge-cross-document-reviewer

Reviews cross-document relationship, precedence, and governing-selection logic in EightForge code changes.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/EricAnalysis/eightforge-os --skill eightforge-cross-document-reviewer-ericanalysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eightforge-cross-document-reviewer
Source: https://github.com/EricAnalysis/eightforge-os/tree/main/.cursor/skills/eightforge-cross-document-reviewer
Command: npx skills add https://github.com/EricAnalysis/eightforge-os --skill eightforge-cross-document-reviewer-ericanalysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When contracts, amendments, exhibits, rate schedules, and invoices interact, it is hard to verify that code changes correctly determine which document governs, which modifies, and which conflicts. This Skill provides a structured review checklist that keeps cross-document reasoning deterministic, evidence-anchored, and auditable. ## Core Features & Use Cases - Relationship Semantics Review: Verifies that attached_to, supplements, modifies, and replaces keep distinct semantics across governing families, amendments, and exhibits. - Precedence and Authority Classification: Classifies findings as PRODUCTION AUTHORITY, PRODUCTION COMPATIBILITY, SHADOW IMPLEMENTED, DESIGN TARGET, or SUPERSEDED/REJECTED, and ensures unresolved precedence stays unresolved rather than falling back to a fabricated answer. - Provenance-Preserving Selection: Checks that governing selections retain competing records, effective-time basis, and operator-readable explanations. - Use Case: When reviewing a pull request that changes how amendments propagate to rate schedules, use this Skill to trace the six-stage resolution sequence and produce a verdict with severity-ordered issues and minimal fixes. ## Quick Start Ask the reviewer to evaluate your pull request affecting document relationships or governing contract selection using the eightforge-cross-document-reviewer checklist.

Frequently Asked Questions about eightforge-cross-document-reviewer

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

FAQPage Schema
How do I review code that resolves precedence between multiple contract documents?▼

Trace the six-stage resolution sequence from source documents through relationship records, precedence resolution, governing selections, validator inputs, and projections. Verify each stage's authority classification and confirm unresolved precedence remains unresolved rather than falling back to a default.

What is the difference between supplements, modifies, and replaces relationships?▼

These relationship types carry distinct semantics: supplements add supporting terms without replacing governing identity, modifies alters an existing document, and replaces supersedes it. The reviewer checks that each type is handled distinctly across governing families, amendments, and exhibits.

Can an exhibit or attachment become the governing document?▼

Exhibits and attachments may supply terms or pricing support but cannot silently replace governing identity. Supplemental context becomes governing authority only through a supported relationship and precedence rule with effective-time evidence.

What happens when document precedence is ambiguous or cyclic?▼

Missing, ambiguous, cyclic, temporally invalid, or contradictory precedence must remain unresolved and visible to operators. The reviewer rejects any fallback selection made merely to produce a governing answer.

When should I use a different reviewer instead of the cross-document reviewer?▼

Route general truth authority and validator lifecycle questions to the truth-engine reviewer, source evidence verification to the document-intelligence reviewer, and audit event storage to the audit reviewer. This reviewer owns only relationship and precedence algorithms.