| name | contract-compare |
| title | Contract Compare — Version Comparison and Favorability Analysis |
| description | Compares two contract versions side-by-side to detect added, removed, and
modified clauses with favorability analysis. Use when a user receives a
revised contract or redline and needs to understand what changed and who
each change favors. Trigger with "/contract-compare" or "compare these
two contracts". |
| author | flight505 |
| author_url | https://github.com/flight505/skill-forge/tree/main/plugins/business-tools/general-legal-assistant/skills/contract-compare |
| license | MIT |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | general |
| practice | contracts |
| language | en |
| tags | ["legal","comparison","redline","negotiation","diff"] |
Contract Compare — Version Comparison and Favorability Analysis
Side-by-side contract comparison skill that identifies every change between two
versions, classifies each change by type and severity, and determines which
party each modification favors. Essential during negotiation rounds when a
counterparty returns a revised draft.
Overview
When a counterparty returns a revised contract, the changes they made — and the
changes they quietly did not make — tell a story about their priorities and
strategy. This skill performs a structured comparison that surfaces not just what
changed, but the strategic significance of each change.
It detects three dangerous patterns that manual review frequently misses:
indemnification drift (gradual shifting of liability across revisions), IP scope
creep (expanding intellectual property assignment through small wording tweaks),
and definition manipulation (redefining key terms to alter clause meaning
without touching the clauses themselves).
Prerequisites
- Two versions of the same contract must be provided, either as:
- Two file paths (e.g.,
contract-v1.pdf and contract-v2.pdf)
- One file path and one pasted text block
- Two pasted text blocks labeled "Version A" and "Version B"
- The user should specify which version is the original (baseline) and which is
the revision. If not specified, assume the first provided is the original.
Instructions
-
Ingest both versions. Read each document in full. If file paths are
provided, use the Read tool.
-
Establish the structural map. Create a section-by-section outline of both
documents. Note any structural changes (sections added, removed, renumbered,
or reordered).
-
Perform clause-level comparison. For each section, classify changes into:
| Change Type | Symbol | Description |
|---|
| Added | + | Entirely new clause or section |
| Removed | - | Clause present in original but absent in revision |
| Modified | ~ | Wording changed within an existing clause |
| Moved | -> | Same content relocated to a different section |
| Unchanged | = |
