Agent skill · Code Review & Quality

contract-review

Contract review skill that adds comment-based issue annotations without changing original text. Enforces a three-layer review (basic, business, legal), writes structured comments (issue type, risk reason, revision suggestion) with risk level encoded via reviewer name, and generates a contract summary, consolidated opinion, and Mermaid business flowchart (with rendered image). Output language must follow the contract’s language.

anbeimegithub.com/anbeimeGitHub ↗
claude-codeships scripts
Install
npx skills add anbeime/skill --skill contract-review --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 27
SKILL.md size: 5 KB
Bundled scripts: yes
Path: skills/legal-assistant-skills-main/contract-review/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 4,714
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Contract Review Skill ## Overview This skill performs contract reviews by **adding comments only** (no edits to the original text). It follows a three-layer review (basic, business, legal) and generates: - Annotated contract (.docx) - Contract summary (.docx) - Consolidated review opinion (.docx) - Business flowchart (Mermaid + rendered image) **Language rule:** detect the contract’s dominant language and output all generated content (comments, summary, opinion, flowchart text) in that language. Use the guidance in **[references/language.md](references/language.md)**. ## Workflow 1. Unpack the contract (.docx) for XML operations 2. Read contract text (pandoc or XML) 3. Execute three-layer review 4. Add comments to the document 5. Generate contract summary 6. Generate consolidated opinion 7. Generate business flowchart and render image 8. Repack to .docx ## Output Naming - Output directory: `审核结果:{ContractName}` for Chinese or `Review_Result_{ContractName}` for English - Reviewed contract: `{ContractName}_审核版.docx` for Chinese or `{ContractName}_Reviewed.docx` for English - Review report: `审核报告.txt` for Chinese or `Review_Report.txt` for English ## Comment Principles - **Comments

What's inside
Steps it walks through
  1. Overview
  2. Workflow
  3. Output Naming
  4. Comment Principles
  5. Review Standards
  6. Layer 1: Basic (text quality)
  7. Layer 2: Business terms
  8. Layer 3: Legal terms
  9. Contract Summary
  10. Consolidated Opinion
  11. Business Flowchart (Mermaid)
  12. Dependencies
  13. Troubleshooting (Short)
  14. Examples
Ships with 24 files
  • LICENSE.txt
  • references/checklist.md
  • references/examples.md
  • references/flowchart.md
  • references/language.md
  • references/opinion.md
  • references/summary.md
  • references/technical.md
  • scripts/__init__.py
  • scripts/contract_analyzer.py
  • scripts/document.py
  • scripts/error_handling.py
  • scripts/mermaid_renderer.py
  • scripts/ooxml/__init__.py
  • scripts/ooxml/pack.py
  • scripts/ooxml/unpack.py
  • scripts/ooxml/validate.py
  • scripts/ooxml/validation/__init__.py
  • scripts/ooxml/validation/base.py
  • scripts/ooxml/validation/docx.py
  • scripts/ooxml/validation/pptx.py
  • scripts/ooxml/validation/redlining.py
  • scripts/opinion_renderer.py
  • scripts/summary_renderer.py
first 24 of 27
More from skill
All skills →
About this skill
What does the contract-review skill do?

Contract review skill that adds comment-based issue annotations without changing original text. Enforces a three-layer review (basic, business, legal), writes structured comments (issue type, risk reason, revision suggestion) with risk level encoded via reviewer name, and generates a contract summary, consolidated opinion, and Mermaid business flowchart (with rendered image). Output language must follow the contract’s language.

How do I install it?

Run `npx skills add anbeime/skill --skill contract-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From anbeime/skill, a repository with 4,714 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going