New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Amendment History

by anthropics in anthropics/claude-for-legal

Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause.

OfficialApache-2.0Auto-check passed

Install Amendment History

skills CLI
$ npx skills add anthropics/claude-for-legal --skill amendment-history -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install anthropics/claude-for-legal amendment-history --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/anthropics/claude-for-legal.git skills-src && mkdir -p .claude/skills && cp -r skills-src/commercial-legal/skills/amendment-history .claude/skills/amendment-history && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
amendment-history
GitHub stars
9.6k
Used in
2 other repos
Token cost
~2.7k tokens
SKILL.md length
1,105 words
Files
1
Skills in repo
147
Repo updated
First seen
Licence
Apache-2.0

At a glance

Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause.

  • Works in 2 steps: Load and order the documents → Read and index
  • The user says what changed in this contract over time
  • SKILL.md covers Instructions, Examples, Matter context and Purpose, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Amendment History is an agent skill from anthropics/claude-for-legal, published by the product's own GitHub organization. Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause. Use when the user says "what changed in this contract over time", "show me the amendment history", "where's the latest [clause]", "how has [provision] evolved", or uploads multiple versions of an agreement.

Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: A suite of plugins for legal workflows. The licence is Apache-2.0.

When your agent uses it

  • The user says what changed in this contract over time
  • Show me the amendment history
  • Wheres the latest [clause]
  • How has [provision] evolved

Example prompts

  • “what changed in this contract over time”
  • “show me the amendment history”
  • “s the latest [clause]”
  • “/amendment-history”

Workflow steps

2 steps, taken from the step headings in SKILL.md.

  1. Load and order the documents
  2. Read and index

What it can do on your machine

Read from SKILL.md and the folder at commit 4a6c651. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Amendment History loads about 2.7k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 1,105 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~98
When it runs · the whole SKILL.md, loaded when a task matches
~2.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from anthropics/claude-for-legal at commit 4a6c651, republished under its Apache-2.0 licence (© anthropics). 1,105 words, ~2,734 tokens.

Download SKILL.mdSave it as .claude/skills/amendment-history/SKILL.md (or your agent's skills folder).
name
amendment-history
description
Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause. Use when the user says "what changed in this contract over time", "show me the amendment history", "where's the latest [clause]", "how has [provision] evolved", or uploads multiple versions of an agreement.
argument-hint
[file(s) | [CLM ID (coming soon)] | [repository link (coming soon)]] [--provision <clause name>]

/amendment-history

Loads a base agreement and all amendments, then either summarizes what changed over time or traces a specific provision to its current controlling language.

Instructions

  1. Get the documents: From file upload, [CLM ID (coming soon)], or [repository link (coming soon)]. Accept multiple files in one invocation. If none provided, ask.

  2. Detect the mode by parsing the request per the mode detection rules below. If a provision name is clearly stated, go straight to Mode 2. If no provision is mentioned, run Mode 1. Ask only if genuinely ambiguous.

  3. Run the workflow below. Follow it fully.

  4. Offer follow-ups after output:

    • "Want me to trace another provision?"
    • "Want a full playbook review of the current agreement as amended?" (routes to vendor-agreement-review)
    • "Want a stakeholder summary of the key changes?" (routes to stakeholder-summary)

Examples

/commercial-legal:amendment-history acme-msa.pdf amendment-1.pdf amendment-2.pdf
/commercial-legal:amendment-history --provision indemnity
/commercial-legal:amendment-history
[paste agreement and amendment text]

Matter context

Matter context. Check ## Matter workspaces in the practice-level CLAUDE.md. If Enabled is ✗ (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run /commercial-legal:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md for matter-specific context and overrides. Write outputs to the matter folder at ~/.claude/plugins/config/claude-for-legal/commercial-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.

Purpose

Contracts accumulate amendments. By the third amendment, nobody remembers what the original said or which version of a clause controls. This skill reads the base agreement and all amendments in chronological order and either summarizes what changed across the whole contract or traces a specific provision through every version to find the current controlling language.

Mode detection

Parse the user's request to determine which mode to run. Do not ask which mode unless the request is genuinely ambiguous.

Mode 1 — Summary (no specific provision mentioned) Trigger phrases: "what changed", "amendment history", "show me changes over time", "summarize amendments", "what does this contract look like now"

Mode 2 — Provision trace (specific clause or topic named) Trigger phrases: "where's the [clause]", "latest [provision]", "how did [term] change", "find the indemnity", "what does it say now about [topic]"

Common provision mappings:

  • "indemnity" / "indemnification" → indemnification section
  • "liability" / "liability cap" → limitation of liability
  • "termination" → term and termination
  • "data" / "privacy" / "DPA" → data protection provisions
  • "IP" / "intellectual property" → IP ownership and licenses
  • "price" / "fees" / "payment" → payment terms
  • "auto-renewal" / "renewal" → renewal mechanics

If the term is ambiguous and maps to more than one provision, list the candidates and ask which one:

"I found [N] provisions related to [term] — [list them]. Which one?"

If the overall request is ambiguous between modes, ask one question:

"Summary of all changes across the contract, or trace a specific provision — like indemnity, liability, or termination?"

Step 1: Load and order the documents

Accept documents from any of these sources:

[CLM integration coming soon] (if connected): Search by counterparty name or agreement title. Pull the base agreement and all amendments. Record metadata typically includes execution dates — use these to establish chronological order.

[Document repository integration coming soon] (if connected): Search by counterparty name or filename. Look for files matching patterns like "Amendment", "Addendum", "Amendment No. 1", "First Amendment", or numbered suffixes. Pull all matches and sort by file date or filename numbering.

Direct upload: User provides files directly. In most cases the ordering is self-explanatory from document titles (e.g., "Amendment No. 1", "Second Amendment", "Addendum A") or dates visible in the filename or document header — proceed without asking.

Only ask the user to confirm ordering if:

  • Filenames give no indication of sequence (e.g., "agreement-final.pdf", "agreement-v2.pdf", "agreement-markup.pdf")
  • Dates are absent from both filenames and document headers
  • Two documents appear to be the same amendment version

If ordering was inferred rather than confirmed, note confidence at the top of the output only where uncertain:

"Order inferred from document titles — one item I was less certain about: [specific document]. Confirm if this affects your review."

Ordering rules:

  • Always establish chronological order before reading content.
  • If execution dates are available in metadata, use them.
  • If not, look for dates in the document header or recitals ("This Amendment, dated as of...").
  • Amendments often reference the agreement they modify ("this Amendment to the Master Services Agreement dated [X]") — use these references to confirm the chain.
Show full SKILL.md (399 more words)Show less

Privilege inheritance

This skill reads the base agreement and amendments — often privileged or confidential in their own right, and typically used for privileged analysis. The output inherits the source's privilege and confidentiality status. Prepend the work-product header from ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md ## Outputs to every output below, distribute only within the privilege circle, and store it where privileged materials live. Strip the header before any external delivery.

Step 2: Read and index

Read each document in chronological order. For each, extract:

  • Document type (base agreement, amendment number, addendum, etc.)
  • Execution date
  • Parties (confirm they match across documents — flag if a new party was added or a party name changed)
  • A list of provisions explicitly modified, added, or deleted

Build a working index before producing output. Use it internally to drive the output — do not show it to the user.

Mode 1: Summary of all changes

Section reference rule

Every finding must include an inline section reference so the reader can verify against the source document without searching:

"Termination for convenience (§12.3): Added. Customer may terminate on 90 days written notice with no fee after the initial term."

If a provision spans multiple sections or the section number changed across amendments, cite all references: "Indemnification (§9.1 base; §9.1 restated in Amendment 5)"

Output format
markdown
# Amendment History: [Counterparty] — [Agreement type]

**Base agreement:** [date]
**Amendments:** [N] ([date of first] → [date of last])
**Last amended:** [date]

---

## What changed — chronological

### Amendment 1 — [date]
**Purpose:** [one sentence — why this amendment existed, from recitals
or clear from context. If not stated, omit rather than guess.]

**Material changes:**
- [Provision] (§[X.X]): [what it said before → what it says now,
  in plain English]
- [New provision added] (§[X.X]): [what it does]
- [Provision deleted] (§[X.X]): [what was removed and why it matters]

### Amendment 2 — [date]
[same structure]

[repeat for each amendment]

---

## Net current state

| Provision | Current position | §Ref | Last changed |
|---|---|---|---|
| [clause] | [plain English summary] | §[X.X] | Amendment N, [date] |
| [clause] | [unchanged from base] | §[X.X] | Base agreement |

---

## Watch items
[Flag anything that looks inconsistent — e.g., an amendment modifying
a provision that was already deleted, contradictory language between
amendments, a party name that changed without a formal assignment,
or a provision where the section number shifted across documents.
Include section references on every flag.]

Mode 2: Provision trace

Output format

Show only what changed. Do not list amendments where the provision was untouched — skip them entirely.

markdown
# Provision Trace: [Provision name]
## [Counterparty] — [Agreement type]

---

### Original — [Base agreement date], §[X.X]
> "[exact quote]"

*Plain English:* [one sentence]

---

### Amendment [N] — [date], §[X.X]

**Was:**
> "[exact quote of prior language]"

**Now:**
> "[exact quote of replacement language]"

*What changed:* [one sentence — practical effect on the parties]

---

[Only subsequent amendments that touched this provision appear here.
All others are omitted.]

---

## Current controlling language

**§[X.X] — [source document, date]**
> "[exact quote]"

*Plain English:* [one sentence]

---

## Watch items
[Flags, inconsistencies, open questions — with section references.
Common items to check: whether the provision is subject to or carved
out of the liability cap; whether the section number shifted across
amendments; whether the amendment language conflicts with another
provision.]

If the provision was never amended after the base agreement:

"This provision has not been modified by any amendment. Original language controls. §[X.X], base agreement, [date]."

Close with the next-steps decision tree

End with the next-steps decision tree per CLAUDE.md ## Outputs. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.

What this skill does not do

  • It does not determine which document controls in the event of a conflict between the base agreement and an amendment — that is a legal interpretation question. It flags conflicts and routes to Legal.
  • It does not draft new amendments.
  • It does not compare against the playbook in ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md — that is the vendor-agreement-review skill's job. This skill is purely historical.
  • It does not infer what an amendment means if the language is ambiguous — it quotes exactly and flags ambiguity for Legal.

© anthropics, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in commercial-legal/skills/amendment-history of anthropics/claude-for-legal.

Open the folder on GitHubat commit 4a6c651

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in anthropics/claude-for-legal, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Amendment History next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Amendment History compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Amendment History this skillanthropics/claude-for-legal9.6k2 repos~2.7kAutomated safety check: PassApache-2.0
Observe Traceruvnet/ruflo74k—~522Automated safety check: NotesMIT
Make Changesremix-run/remix33k—~2.4kAutomated safety check: PassMIT
Master Agreement Generatoraffaan-m/ECC276k—~2.9kAutomated safety check: PassMIT
Orch Change Featureaffaan-m/ECC276k1 repos~420Automated safety check: PassMIT
Amendment HistoryZekaiSuni/claude-for-legal-turkish107—~1.3kAutomated safety check: PassApache-2.0

Similar skills

  • Observe Trace

    ruvnet/ruflo

    Trace agent execution by collecting spans and building a trace tree for a task

    74k GitHub stars~522 tokensUpdated today
    Auto-check: notes

  • Make Changes

    remix-run/remix

    Create or update Remix repo change files under packages//.changes.

    33k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Master Agreement Generator

    affaan-m/ECC

    Builds DRAFT counterparty agreements from one markdown template and a small JSON spec per party, with clauses picked by the party's role.

    276k GitHub stars~2.9k tokensUpdated today
    Legal & ComplianceAuto-check passed

  • Orch Change Feature

    affaan-m/ECC

    Orchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to match, review, and gated commit.

    276k GitHub starsUsed in 1 repo~420 tokens
    Auto-check passed

  • Amendment History

    ZekaiSuni/claude-for-legal-turkish

    Trace how a contract has changed across its base agreement and all amendments, ek protokoller, zeyilnameler, and related variation documents.

    107 GitHub stars~1.3k tokensUpdated 4 mo ago
    Auto-check passed

  • Change Management

    sickn33/agentic-awesome-skills

    Implement change management processes. An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~3.5k tokens
    DevOps & CloudAuto-check passed

More from anthropics/claude-for-legal

All 147 skills in this repo

  • Legal Clinic Client Intake

    anthropics/claude-for-legal

    Official

    Structures a legal clinic client intake interview and produces a case summary with cross-area issue spotting, conflict flags and triage classification.

    9.6k GitHub starsUsed in 3 repos~3.2k tokens
    Auto-check passed

  • Supervisor Review Queue

    anthropics/claude-for-legal

    Official

    Holds student work in a queue for a legal clinic professor to approve, edit-then-approve or return before anything reaches clients or courts.

    9.6k GitHub starsUsed in 3 repos~1.1k tokens
    Auto-check passed

  • Tabular Document Review

    anthropics/claude-for-legal

    Official

    Builds a review grid with one row per document and one column per data point, each cell cited to a verbatim quote, built for M&A diligence and other batch reviews.

    9.6k GitHub starsUsed in 3 repos~4.3k tokens
    Auto-check passed

  • Product Launch Legal Review

    anthropics/claude-for-legal

    Official

    Runs a category-by-category legal review of a product launch from a PRD or tracker ticket, calibrated to your team's framework, and writes a review memo in house format.

    9.6k GitHub starsUsed in 2 repos~5k tokens
    Auto-check passed

  • Legal Skills Registry Browser

    anthropics/claude-for-legal

    Official

    Searches watched registries for community legal skills, shows matches with descriptions and offers the full SKILL.md before anything is installed.

    9.6k GitHub starsUsed in 2 repos~620 tokens
    Auto-check passed

  • Contract Renewal Tracker

    anthropics/claude-for-legal

    Official

    Shows which contracts renew soon and when notice must be sent by, working from a maintained renewal register, and warns about missed cancellation windows.

    9.6k GitHub starsUsed in 2 repos~3.1k tokens
    Auto-check passed

Questions about Amendment History

What does Amendment History do?

Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause. Amendment History is an agent skill from anthropics/claude-for-legal, published by the product's own GitHub organization. Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause.

When should I use Amendment History?

Amendment History fits situations like: the user says what changed in this contract over time; show me the amendment history; wheres the latest [clause]; how has [provision] evolved.

How do I install Amendment History in Claude Code?

Run `npx skills add anthropics/claude-for-legal --skill amendment-history -a claude-code`. Or copy the skill folder (commercial-legal/skills/amendment-history in anthropics/claude-for-legal) into .claude/skills/amendment-history in your project. Claude Code loads it when a task matches its description.

How do I install Amendment History in Codex?

Run `npx skills add anthropics/claude-for-legal --skill amendment-history -a codex`. Or copy the skill folder (commercial-legal/skills/amendment-history in anthropics/claude-for-legal) into .agents/skills/amendment-history in your project. Codex loads it when a task matches its description.

Can I use Amendment History in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add anthropics/claude-for-legal --skill amendment-history -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/amendment-history, .gemini/skills/amendment-history, .github/skills/amendment-history and .opencode/skills/amendment-history in your project.

What does Amendment History need to run?

SKILL.md names no scripts, command-line tools or credentials: Amendment History is instructions for the agent only.

Does Amendment History access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Amendment History safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Amendment History use?

Amendment History is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Amendment History use?

About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Amendment History?

Skills that share tags, products or a category with Amendment History: Observe Trace (ruvnet/ruflo, 74k stars), Make Changes (remix-run/remix, 33k stars), Master Agreement Generator (affaan-m/ECC, 276k stars) and Orch Change Feature (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Amendment History?

anthropics (a GitHub organization, an official publisher) maintains it in anthropics/claude-for-legal, which has 9,633 GitHub stars. The repository holds 147 skills in this directory. The repository was last updated on September 29, 2026.

Source: anthropics/claude-for-legal on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.