review

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/review

/review

Reviews an inbound agreement against the playbook in
~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md
. Identifies the agreement structure from titles, selects the appropriate skill(s), and — if confirm_routing is enabled — checks with the user before proceeding.
根据
~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md
中的操作手册审核外来协议。从标题识别协议结构,选择合适的技能,并且如果启用了confirm_routing,会在继续操作前与用户确认。

Instructions

操作说明

  1. Load
    ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md
    .
    If placeholders present, stop and prompt: "Run
    /commercial-legal:cold-start-interview
    first — I need to learn your playbook before I can review against it."
    Also read
    ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md
    ## Review preferences
    confirm_routing
    . If the field is missing, treat it as
    true
    .
  2. Get the agreement: From file path, Drive link, [CLM ID], or pasted text. If none provided, ask.
  3. Read the document structure — titles first.
    Before reading the body, extract:
    • The main agreement title (e.g., "Master Services Agreement", "Non-Disclosure Agreement")
    • All exhibit, schedule, addendum, and attachment titles (e.g., "Exhibit A — Data Processing Addendum", "Schedule 1 — Subscription Order Form", "Annex B — Service Level Agreement")
    This is the routing signal. Do not rely on body keywords alone — a 40-page MSA with "confidential" throughout is not an NDA.
  4. Select the skill(s) based on document structure.
    Map each identified document or section to a skill:
    Document / section title containsSkill
    Non-Disclosure, NDA, Confidentiality Agreement (as the main agreement)nda-review
    Master Services Agreement, Professional Services, Statement of Work, Consulting Agreementvendor-agreement-review
    Subscription, SaaS, Cloud Services, Order Form with auto-renewal, Software License with recurring feessaas-msa-review (overlay on vendor-agreement-review)
    Data Processing Addendum, DPA, Data Processing Agreement (as exhibit or standalone)note for vendor-agreement-review → data protection section
    Service Level Agreement, SLA (as exhibit)note for saas-msa-review → SLA section
    Multiple skills may apply. Common combinations:
    • MSA + DPA exhibit → vendor-agreement-review, with DPA noted
    • SaaS subscription + Order Form + SLA exhibit → saas-msa-review (covers all three)
    • MSA + Order Form with auto-renewal → vendor-agreement-review + saas-msa-review overlay
    When the structure is genuinely ambiguous after reading titles (e.g., a document titled "Agreement" with no exhibits listed), read the first two pages of the body to resolve it — then stop and route.
  5. Confirm routing if enabled.
    If
    confirm_routing
    is
    true
    in
    ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md
    (or field is absent):
    I'm going to review this as: [agreement type(s)].
    
    Documents identified:
    - [Main agreement title] → [skill]
    - [Exhibit A title] → [how it will be handled]
    - [Exhibit B title] → [how it will be handled]
    
    Sound right? (yes / no — or tell me what I got wrong)
    Wait for confirmation before proceeding. If the user corrects the routing, apply their instruction and proceed.
    If
    confirm_routing
    is
    false
    : proceed silently. Log the routing decision at the top of the review memo so the user can see what was applied.
  6. Run the skill(s). Follow each skill's workflow fully. If multiple skills apply, run them in sequence and integrate the output into a single memo — don't produce separate memos.
  7. Check for escalations: If any issue exceeds the reviewer's authority per the
    ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md
    matrix, invoke escalation-flagger to route and draft the ask.
  8. Offer follow-ups:
    • Stakeholder summary for the business owner
    • Redline .docx with tracked changes
    • [CLM] record creation (if connected)
    • Add to renewal register (if auto-renewal found)
  1. 加载
    ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md
    。如果存在占位符,请停止操作并提示:“请先运行
    /commercial-legal:cold-start-interview
    ——我需要先了解你的操作手册,才能进行审核。”
    同时读取
    ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md
    ## Review preferences
    confirm_routing
    字段。如果该字段缺失,默认视为
    true
  2. 获取协议文件:可通过文件路径、Drive链接、[CLM ID]或粘贴文本获取。若未提供任何信息,请询问用户。
  3. 先读取文档结构——标题优先
    在读取正文前,提取以下内容:
    • 主协议标题(例如:“Master Services Agreement”“Non-Disclosure Agreement”)
    • 所有附件、附录、补充协议的标题(例如:“Exhibit A — Data Processing Addendum”“Schedule 1 — Subscription Order Form”“Annex B — Service Level Agreement”)
    以上内容是匹配技能的依据。请勿仅依赖正文关键词——一份40页且通篇包含“confidential”的MSA并非NDA。
  4. 根据文档结构选择技能
    将识别出的每份文档或章节映射到对应技能:
    文档/章节标题包含技能
    Non-Disclosure、NDA、Confidentiality Agreement(作为主协议)nda-review
    Master Services Agreement、Professional Services、Statement of Work、Consulting Agreementvendor-agreement-review
    Subscription、SaaS、Cloud Services、含自动续订条款的Order Form、含 recurring fees的Software Licensesaas-msa-review(作为vendor-agreement-review的补充)
    Data Processing Addendum、DPA、Data Processing Agreement(作为附件或独立文档)标注给vendor-agreement-review → 数据保护章节
    Service Level Agreement、SLA(作为附件)标注给saas-msa-review → SLA章节
    可能存在多个技能适用的情况。常见组合:
    • MSA + DPA附件 → 使用vendor-agreement-review,并标注DPA相关内容
    • SaaS订阅协议 + Order Form + SLA附件 → 使用saas-msa-review(覆盖全部三类文档)
    • MSA + 含自动续订条款的Order Form → 使用vendor-agreement-review + saas-msa-review补充
    若读取标题后结构仍存在歧义(例如:文档标题仅为“Agreement”且未列出任何附件),请读取正文前两页以明确类型——之后停止读取并匹配技能。
  5. 若启用则确认技能匹配
    ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md
    中的
    confirm_routing
    true
    (或字段缺失):
    我将按以下类型审核:[协议类型]。
    
    识别到的文档:
    - [主协议标题] → [对应技能]
    - [附件A标题] → [处理方式]
    - [附件B标题] → [处理方式]
    
    是否正确?(是/否——或告诉我哪里有误)
    等待用户确认后再继续操作。若用户纠正了技能匹配方式,请按照用户指示执行。
    confirm_routing
    false
    :直接继续操作。在审核备忘录顶部记录技能匹配决策,以便用户查看。
  6. 运行技能:完整遵循每个技能的工作流程。若适用多个技能,请依次运行并将输出整合为一份单一备忘录——不要生成单独的备忘录。
  7. 检查是否需要升级处理:若任何问题超出了
    ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md
    矩阵中审核人员的权限范围,请调用escalation-flagger来分配处理并起草需求。
  8. 提供后续服务选项
    • 给业务负责人的利益相关者摘要
    • 带修订痕迹的Redline .docx文件
    • 创建[CLM]记录(若已连接)
    • 添加到续订注册表(若发现自动续订条款)

Configuring confirm_routing

配置confirm_routing

Add to
~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md
## Review preferences
:
markdown
undefined
~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md
## Review preferences
中添加:
markdown
undefined

Review preferences

Review preferences

confirm_routing: true # Set to false to skip routing confirmation and proceed automatically

The cold-start interview should ask about this preference. Default is `true` — confirmation on. As trust builds, the user can set it to `false`.
confirm_routing: true # 设置为false可跳过技能匹配确认,自动继续操作

初始化访谈会询问此偏好设置。默认值为`true`——即开启确认功能。随着信任度提升,用户可将其设置为`false`。

Examples

示例

/commercial-legal:review vendor-msa.pdf
/commercial-legal:review https://drive.google.com/file/d/ABC123
/commercial-legal:review
[paste agreement text]
/commercial-legal:review vendor-msa.pdf
/commercial-legal:review https://drive.google.com/file/d/ABC123
/commercial-legal:review
[paste agreement text]

Output

输出

Full review memo per the skill's format. Routing decision logged at the top. Deviation-by-deviation, specific redline language, named approver. Saved where
~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md
→ House style says work product goes.
按照技能格式生成完整的审核备忘录。技能匹配决策记录在顶部。逐条列出差异、具体修订措辞、指定审批人。保存位置遵循
~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md
→ House style中规定的工作产品存储路径。