← ClaudeAtlas

compare-contract-versionslisted

Compare two versions of the same agreement and report exactly what changed — clauses added, removed or reworded, altered amounts, dates and party names, renumbered sections, and changes to the signature blocks. Use when someone has a revised draft, a counterparty's markup or a redline, when they ask what changed, what came back different, whether their edits survived, or what the other side quietly altered.
mypropper/skills · ★ 1 · Data & Documents · score 72
Install: claude install-skill mypropper/skills
# Compare contract versions Read two versions of the same document and report every substantive difference, with locations and both wordings. This runs entirely locally and calls no Propper tools, so it works with or without an account. For a single document about to go out, use `signature-ready-check`. For dates and deadlines out of a final document, use `extract-contract-dates`. ## Steps ### 1. Establish which version is which Direction matters: "added" and "removed" are meaningless without a baseline. Take the earlier version as the baseline and the later one as the comparison. When the filenames do not settle it, ask. Do not infer recency from a modification time, which reflects when a file was copied as often as when it was edited. ### 2. Extract the text before comparing Pull plain text from both. Then discard differences that are not content: - line wrapping, pagination, page numbers, headers and footers - whitespace runs, smart quotes versus straight quotes, hyphenation at line ends - font, spacing and styling changes carrying no text change Reporting reflow as change buries the three edits that matter under two hundred that do not. ### 3. Align by clause, not by line Match sections by their numbering and headings first, then compare within each matched pair. A line-by-line diff of a document where one paragraph was inserted early reports every subsequent line as changed. Renumbering is itself a finding. When section 8 becomes section 9, say so, and check