菜单
Trace how a contract has changed across its base agreement and all amendments, ek protokoller, zeyilnameler, and related variation documents. Produces either a chronological summary of all changes or a provision trace for a specific clause while preserving the original skill function.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | amendment-history |
| description | Trace how a contract has changed across its base agreement and all amendments, ek protokoller, zeyilnameler, and related variation documents. Produces either a chronological summary of all changes or a provision trace for a specific clause while preserving the original skill function. |
| argument-hint | [file(s) | CLM ID | repository link | matter slug] [--provision <clause name>] |
Ana sözleşme ile ek protokol, zeyilname, tadil sözleşmesi, devir/temlik metni ve yan yazılar arasındaki değişiklik zincirini çıkarır. Nihai hukuki yorum vermez; hangi metnin hangi hükmü nasıl değiştirdiğini gösterir ve çelişkileri hukukçu incelemesine taşır.
Get the documents. Accept direct upload, CLM/repository link, KEP or e-signature package, or matter folder. UYAP only applies if the contract history is tied to a court/enforcement file.
Detect the mode.
Establish chronology before substance. Use, in order:
Read and index every document. Extract type, parties, execution date, effective date, modified/deleted/added provisions, signatures, and source confidence.
Flag uncertain ordering. If order is inferred and confidence is low, ask for confirmation before final output.
If matter workspaces are enabled, load the active matter and write outputs there. Never cross-read other matters unless allowed and requested.
Classify documents by their own title and operative language:
If unclear, mark as muhtemel belge türü.
For each document:
belge:
tur:
imza_tarihi:
yururluk_tarihi:
kaynak:
siralama_guveni: yuksek | orta | dusuk
taraflar:
degistirilen_maddeler:
Check whether a party name changed, a party was added, an assignment occurred, or signature authority differs across documents.
Every finding must include section references:
Süreli fesih (m. 12.3; 2 No'lu Ek Protokol m. 4 ile değişik): 90 gün önceden bildirimle fesih hakkı eklendi.
# Sözleşme Tadil Geçmişi: [Counterparty] - [Agreement type]
**Ana sözleşme:** [date]
**Tadil belgeleri:** [N] ([first date] -> [last date])
**Son değişiklik:** [date]
**Sıralama güveni:** [yüksek / orta / düşük]
## Değişiklik Kronolojisi
### [Belge türü] [N] - [date]
**Amaç:** [recitals or omit if unknown]
**Esaslı değişiklikler:**
- [Provision] (m. [X]): [old -> new in plain Turkish]
- [Added provision] (m. [X]): [effect]
- [Deleted provision] (m. [X]): [why it matters]
## Güncel Net Durum
| Hüküm | Güncel pozisyon | Atıf | Son değişiklik |
|---|---|---|---|
| [clause] | [plain Turkish] | m. [X] | [document/date] |
## Dikkat Edilecek Hususlar
[inconsistencies, numbering shifts, assignment issues, signature issues]
Show only documents that touched the provision. Skip untouched amendments.
# Madde Takibi: [Provision]
## [Counterparty] - [Agreement type]
### Orijinal Metin - [Base date], m. [X]
> "[short exact quote]"
**Özet:** [one sentence]
### [Belge türü] [N] - [date], m. [X]
**Eski hali:** "[quote]"
**Yeni hali:** "[quote]"
**Ne değişti:** [practical effect]
## Güncel ve Geçerli Görünen Hüküm
**m. [X] - [source document, date]**
> "[quote]"
## İzleme Notları
[conflicts, missing signatures, limitation cap effects, numbering shifts]
If never amended:
Bu hüküm tadil belgeleriyle değiştirilmemiş görünüyor. Ana sözleşmedeki metin kontrol eden metindir; yine de çelişkili genel hükümler ayrıca incelenmelidir.
Do not decide which document legally prevails when there is conflict. Instead:
Use:
Bu hükümler arasında potansiyel çelişki var. Hangi hükmün üstün geleceği sözleşmenin yorumuna ve varsa öncelik sırası maddesine bağlıdır; hukukçu incelemesine yönlendirilmelidir.
EU AI Act (ve Türkiye uyumu) per-system inventory — track each AI system's role (provider, deployer, importer, distributor, authorized representative, product manufacturer) and risk tier (prohibited, high-risk, limited, minimal, GPAI, GPAI+systemic). Role and tier are assessed per system, not per company. Use when the user says "ai inventory", "add an ai system", "what systems do we have", "classify this ai system", "eu ai act register", or "ai system registry".
Run an AI impact assessment — structured intake, risk analysis, regulatory classification per regime in scope, policy consistency diff, and recommendation with conditions. Uses the house-style structure learned from the seed impact assessment in `~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md`. Use when user says "impact assessment for", "assess this AI use case", "run an AIA", "generate an AIA", "we need to document this AI system", "AI risk assessment for X", or follows a conditional triage result.
Run the cold-start interview — learns your AI governance practice and writes `~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md` from your AI policy, a reference impact assessment, and key vendor AI agreements. Use when the practice profile is missing or contains `[PLACEHOLDER]` markers, or when user says "set up ai governance plugin", "onboard me", "configure ai governance".
Guided customization of your AI governance practice profile — change one thing without re-running the whole cold-start interview. Adjust risk posture, escalation contacts, use-case registry entries, vendor AI positions, AI policy commitments, impact-assessment house style, or matter workspace paths. Use when the user says "change my [thing]", "update my profile", "edit my config", "tune my playbook", or "customize".
Draft a firm AI usage policy from published model policies, adapted to your practice profile — a research-and-synthesis tool whose output is a draft for attorney review and adoption, not a finished policy. Use when user says "draft an AI policy", "we need an AI policy", "build an AI usage policy", "our firm needs a GenAI policy", or similar requests to generate a first-cut internal AI policy.
Diff a new AI regulation or guidance against your current governance posture — surfaces gaps, priorities, and a remediation plan with owners and deadlines. Use when an AI regulation moves (or you learn about one you missed), or when user says "new reg just dropped", "does [regulation] affect us", "gap analysis for EU AI Act (ve Türkiye uyumu)", "compliance check against [AI law or guidance]", or pastes regulatory text.