cs-review

Reviews diffs, design documents, and repository audits with graded findings in a single read-only pass.

1.1k|83|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/liuzhengdongfortest/easysdd --skill cs-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cs-review
Source: https://github.com/liuzhengdongfortest/easysdd/tree/main/plugins/codestable/skills/cs-review
Command: npx skills add https://github.com/liuzhengdongfortest/easysdd --skill cs-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code changes and design proposals often ship without independent scrutiny, letting correctness, security, and contract issues slip through. This Skill performs a single-round, read-only review of a frozen target and returns graded findings with file and line references.

Core Features & Use Cases

  • Diff Review: Reviews the current working-tree diff or a specified git range against the stated intent of the change, classifying findings as blocking, important, or nit.
  • Design and Contract Review: Checks requirement coverage, contract impact, shared terminology, and risks in design documents or task packets before implementation proceeds.
  • Repository Audit: Performs read-only audits of a user-defined scope such as a directory or a dimension like security or performance.
  • Use Case: Before merging a feature branch, invoke the review on the staged diff to receive a verdict of mergeable, conditionally mergeable, or change-first, with each finding tied to a file and line number.

Quick Start

Ask the assistant to review the current diff with cs-review and return graded findings with a merge conclusion.

Frequently Asked Questions about cs-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a git diff before merging?

Invoke the review on the current working-tree diff by default, or pass a specific git range with the --range option. The reviewer compares the changes against the stated intent and returns findings graded as blocking, important, or nit with file and line references.

How to review a design document before implementation?

Submit the design document version or a task packet containing the full text and its SHA-256 hash as the frozen review target. The review checks requirement coverage, contract impact, shared terminology consistency, and risks without modifying the document.

Can the reviewer fix the issues it finds?

No, the review is strictly read-only and never modifies code or business files. Fixes are handled by the calling workflow, which may send a follow-up with the new frozen target and a fix summary to the same reviewer session for re-review.

What happens when review context is insufficient?

The review returns a NeedsContext result listing the missing items and the scope already checked. It never ends with an idle or empty state, and every invocation must produce a terminal review result.

When should I use a repository audit instead of a diff review?

Use audit mode when you want a proactive scan of a whole repository, a directory, or a dimension such as security or performance rather than a specific change. For large scopes, align with the user first on where to scan and what to look for.