historial-adendas

Compare base mercantile contracts with chronological addenda to extract clause-level changes.

35|19|Updated May 15, 2026
One-click install
npx skills add https://github.com/betobetico/claude-para-abogados --skill historial-adendas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: historial-adendas
Source: https://github.com/betobetico/claude-para-abogados/tree/main/mercantil/skills/historial-adendas
Command: npx skills add https://github.com/betobetico/claude-para-abogados --skill historial-adendas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of not knowing how a mercantile contract’s key clauses changed over time across successive addenda, creating uncertainty about the effective wording and potential inconsistencies.

Core Features & Use Cases

  • Timeline reconstruction by clause: Builds a temporal evolution table per trackable clause, starting from the base contract through each chronological addenda.
  • Change direction and versioning: Captures the original clause, each modification with date and source reference, the current version, and whether the change tends to favor one side.
  • Inconsistency detection: Flags contradictions between modified vs. non-modified clauses, incorrect clause numbering references, cross-reference drift in definitions, and conflicts between versions without express derogation.
  • Use Case: Ideal for legal review in Spain when you receive a base commercial contract plus multiple amendment documents and need a structured view of what actually changed and where.

Quick Start

Use historial-adendas by providing the base contract path followed by the paths of all adenda in chronological order, and ask for a clause-by-clause evolution report with inconsistencies highlighted.

Frequently Asked Questions about historial-adendas

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

FAQPage Schema
How do I track changes across multiple contract addenda over time?

Detecting inconsistencies in modified contracts involves flagging contradictions between updated and non-updated clauses, incorrect numbering references, and definition cross-reference drift. These conflicts are identified without deciding legal precedence, producing a structured markdown report for review.

How do I reconstruct a clause timeline from a base contract and its amendments?

Contract amendment analysis captures whether each modification tends to favor one side, flagging directional changes alongside the extracted text. This versioning approach records the original clause, each modification with source references, and the current version without determining legal precedence.

Can I use this for mercantile law contracts with shifting clause numbering?

Yes, this works for mercantile law contracts where clause text, numbering, definitions, or cross-references shift across amendments. The analysis detects additions, modifications, and deletions per clause despite numbering inconsistencies across the amendment documents.

What are the limitations of automated contract consolidation analysis?

Automated contract consolidation analysis produces a structured markdown report highlighting changes and inconsistencies but does not decide legal precedence. It is limited to detecting contradictions, numbering errors, and cross-reference drift without providing legal interpretation or binding conclusions.