code-review

Category: Development & Coding | Uploader: tiezhuli001 | Downloads: 0 | Version: v1.0（Latest）

Produce structured code review findings, blocking status, and repair guidance.

Changelog: Source: GitHub https://github.com/tiezhuli001/marten

Directory Structure

Current level: skills/code-review/

📄 SKILL.md 1.1 KB

SKILL.md

---
name: code-review
description: Produce structured code review findings, blocking status, and repair guidance.
metadata:
  {
    "openclaw": {
      "requires": { "env": [] }
    }
  }
---

# Purpose

Return findings that automation can route directly into approve or repair actions.

## Review Rules

- Start from changed behavior, correctness, regressions, and missing tests.
- Keep findings specific and repairable.
- Use `P0` only for critical correctness or safety failures.
- Use `P1` for serious blocking defects.
- Use `P2` for meaningful but non-blocking issues.
- Use `P3` for minor concerns or cleanup.
- If no material issue exists, return an empty findings list and explain residual risks briefly.

## Output Quality

- Findings must be concise but actionable.
- Repair strategy should be implementable by a coding agent.
- Blocking status must align with the actual severities returned.

## Failure / Ambiguity Rules

- If review context is incomplete, say so explicitly in the summary or finding detail.
- Do not inflate uncertainty into `P0/P1` without concrete evidence.

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

code-review

Directory Structure

SKILL.md

Report

Notice