SuperAPI AI Directory

amendment-history

Office & productivity

View repository

Updated 10-16 05:04

About this skill

/amendment-history

Load the base agreement and all amendments, then summarize the changes over time or track the currently effective language of a specific clause.

Instructions

  1. Get files: From file upload, contract management system ID (coming soon), or repository link (coming soon). Accept multiple files in one call. If not provided, ask.

  2. Detect mode Determine the operating mode by parsing the request. Clearly specifies a clause name → Mode 2. No clause mentioned → Mode 1. Ask only when there is genuine ambiguity.

  3. Run the following workflow. Execute fully.

  4. After output, provide follow-up actions:

    • "Do you need to track other clauses?"
    • "Do you need a complete review guidance review of the amended current agreement? (Route to supplier agreement review)"
    • "Do you need a stakeholder summary of key changes? (Route to stakeholder summary)"

Examples

/commercial-legal:amendment-history acme-msa.pdf amendment-1.pdf amendment-2.pdf
/commercial-legal:amendment-history --provision 赔偿
/commercial-legal:amendment-history
[粘贴协议和修订文本]

Matter Context

Matter Context. Check the business domain-level CLAUDE.md for ## 事项工作区. If Enabled is ✗(the default for legal users), skip the rest of this paragraph. If enabled and there is no active matter, ask. Load the active matter's matter.md。


Purpose

Contracts continuously accumulate amendments. By the third amendment, no one remembers what the original said or which clause version is currently effective. This skill reads the base agreement and all amendments in chronological order, summarizes the changes to the entire contract, or tracks the currently effective language of a specific clause.

Mode Detection

Mode 1 — Summary(No specific clause mentioned) Trigger phrases: "what changed," "revision history," "show changes over time"

Mode 2 — Clause Tracking(Specific clause or topic specified) Trigger phrases: "where is [clause]," "latest [clause]," "how has [clause] changed"

Common clause mapping:

  • "Indemnification" → Indemnification section
  • "Liability" "Liability cap" → Limitation of liability
  • "Termination" → Term and termination
  • "Data" "Privacy" "Data processing agreement" → Data protection clauses
  • "Intellectual property" → Intellectual property ownership and licensing
  • "Price" "Fees" "Payment" → Payment terms
  • "Auto-renewal" "Renewal" → Renewal mechanism

Step 1: Load and order files

Accept files from the following sources:

Contract management system integration (coming soon): Search by counterparty name. Get the base agreement and all amendments.

Direct upload: The user provides files directly. In most cases the file titles are self-explanatory ("Amendment Agreement One," "Second Amendment Agreement"). Ask the user to confirm the order only in the following cases: the file names have no order indicator, dates are missing, or two files appear to be the same amendment version.

Ordering rules: Always establish chronological order before reading the contents. Use execution dates, document header dates, or amendment numbers.


Confidentiality Privilege Inheritance

This skill reads the base agreement and amendments—these documents are themselves typically confidential. Output inherits the confidentiality status of the source documents. Prefix output with a work product header and distribute only within the confidentiality privilege circle.

Step 2: Read and Index

Read each document in chronological order. Extract: document type, execution date, parties, and a list of clauses expressly modified/added/deleted. Build an internal working index.


Mode 1: All Changes Summary

Output Format

# 修订历史:[对方当事人] — [协议类型]

**基础协议:** [日期]
**修订:** [N]份([首份日期] → [末份日期])
**最后修订:** [日期]

---

## 变更内容——按时间顺序

### 修订一 — [日期]
**目的:** [一句话——此修订存在的原因]

**实质变更:**
- [条款](§[X.X]):[变更前 → 变更后]

[每份修订重复]

---

## 现行有效状态

| 条款 | 当前立场 | §引用 | 最后变更 |
|---|---|---|---|
| [条款] | [中文摘要] | §[X.X] | 修订N, [日期] |
| [条款] | [与基础协议一致] | §[X.X] | 基础协议 |

---

## 观察事项
[标注不一致之处——如修订修改了已删除的条款、修订间矛盾语言、名称变更等。每项标注附带条款引用。]

Mode 2: Clause Tracking

# 条款追踪:[条款名称]
## [对方当事人] — [协议类型]

---

### 原版 — [基础协议日期], §[X.X]
> "[精确引用原文]"

*中文说明:* [一句话]

---

### 修订[N] — [日期], §[X.X]

**曾为:**
> "[先前的精确引用]"

**现为:**
> "[替代语言的精确引用]"

*变更内容:* [一句话——对当事人的实际影响]

---

[仅包含触及该条款的后续修订。其他省略。]

---

## 现行有效语言

**§[X.X] — [来源文件, 日期]**
> "[精确引用原文]"

*中文说明:* [一句话]

---

## 观察事项
[标志、不一致、待解决问题——附带条款引用。]

If a clause was never amended: "> This clause was not modified by any amendment. The original language remains in effect. §[X.X], Base Agreement, [date]."


Close with the Next-Step Action Decision Tree

Close with the next-step action decision tree in CLAUDE.md ## 输出 . The decision tree is the output; the lawyer chooses.

What This Skill Does Not Do

  • Does not determine which document prevails when the base agreement and an amendment conflict—that is a question of legal interpretation. Flag the conflict and route to Legal.
  • Does not draft new amendments.
  • Does not compare against review guidelines—that is the job of the vendor agreement review skill. This skill is purely historical tracking.