amendment-history

Name: amendment-history
Availability: InStock
Author: az9713

Trace contract changes across base agreements and amendments with quoted provenance.

Updated May 15, 2026

Search Tags:#document comparison #clause tracing #section references #contract amendments #provision history #privileged analysis

Ready to run

npx skills add https://github.com/az9713/claude-for-legal-tutorial --skill amendment-history-az9713

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: amendment-history
Source: https://github.com/az9713/claude-for-legal-tutorial/tree/main/commercial-legal/skills/amendment-history
Command: npx skills add https://github.com/az9713/claude-for-legal-tutorial --skill amendment-history-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Contracts accumulate amendments, and it becomes hard to remember what the base agreement originally said versus what the latest controlling language now requires.

Core Features & Use Cases

Chronological amendment summaries: Produces a timeline of what changed across the base agreement and subsequent amendments.
Clause-level provision tracing: Follows a specific clause (e.g., indemnity, liability cap, termination, privacy/DPA, IP, payment) through each touched version to identify current controlling language with exact quotes.
Citation and watch items: Includes inline section references on each finding and flags inconsistencies such as conflicting amendments, section shifts, party name changes, or modifications to provisions that appear deleted.

Quick Start

Ask the skill to trace the latest version of a clause by running: /commercial-legal:amendment-history --provision indemnity

Frequently Asked Questions about amendment-history

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

FAQPage Schema

How do I trace the latest controlling language for a specific contract clause through multiple amendments?▼

You can trace a specific provision by running a command like `/amendment-history --provision [clause_name]`. The skill parses your intent, loads and orders the documents chronologically, and outputs the latest controlling language with verbatim quotes and section references.

What is the best way to compare multiple versions of an agreement and see what changed over time?▼

Producing a chronological amendment timeline is the best way to compare multiple agreement versions. The skill extracts section-referenced change sets from uploaded documents to show exactly how a contract evolved from its base agreement through all amendments.

Can I generate a full amendment timeline from a base contract and its subsequent modifications?▼

Yes, you can generate an end-to-end amendment timeline. The skill loads your base agreement and amendments, orders them chronologically, and produces a timeline summarizing what changed at each stage of the contract's evolution.

Does the amendment history analysis flag inconsistencies like conflicting amendments or section shifts?▼

Yes, the analysis flags inconsistencies such as conflicting amendments, section shifts, party name changes, or modifications to provisions that appear deleted. These watch items are included alongside inline section references on each finding.

How do I get verbatim quotes with provenance when tracking contract provision history?▼

The skill outputs verbatim quotes with provenance by extracting section-referenced change sets from the loaded documents. It ensures every finding in the clause-level provision history includes exact quotes and inline section references for traceability.

What kind of contract clauses can I track through different agreement versions?▼

You can track various clauses such as indemnity, liability cap, termination, privacy/DPA, IP, and payment provisions. The skill follows the specific clause through each touched version to identify the current controlling language.