跳到主要内容
知仓学习社ZHICANG

six-dimension-code-review

Structured pull-request review across six fixed dimensions — correctness, clarity, consistency, coverage, complexity, and change-scope — producing a…

不碰外部(只输出文字)无严重或高危命中a5c-ai/babysitter

它会碰到什么

扫了多少1 个文本文件,3 KB
它会碰到什么不碰外部(只输出文字)
命中总数0 处
命中统计严重 0 · 高 0 · 中 0 · 低 0

这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。

技能内容

Six-Dimension Code Review

The rubric hardcoded as the DIMENSIONS array in

[../../code-review/six-dimension-review.js](../../code-review/six-dimension-review.js)

(@process specializations/collaboration/code-review/six-dimension-review) and depended on

by [../../github/pr-lifecycle-feature.js](../../github/pr-lifecycle-feature.js). Each

dimension is reviewed independently and in parallel; one lens per pass.

The six dimensions

  • correctness — Does the code do what the PR claims? Any logical bugs, off-by-one,

race conditions, null/undef hazards, error-path gaps?

  • clarity — Is intent obvious from the code? Names, structure, comments where

non-obvious. Flag cleverness that sacrifices readability.

  • consistency — Does the change match existing patterns, conventions, and

architectural boundaries in the repo?

  • coverage — Are there tests for the new behavior? Do existing tests still exercise

the right paths? Any coverage gaps for edge cases?

  • complexity — Is the solution as simple as it can be? Any over-engineering,

premature abstraction, unused flexibility?

  • change-scope — Is the PR focused on one concern? Any drive-by edits, mixed

refactor+feature, or churn that belongs in a separate PR?

Output shape

Each dimension pass returns:

{
  "findings": [
    {
      "severity": "block",
      "path": "src/example.ts",
      "line": 42,
      "detail": "…",
      "suggestion": "…"
    }
  ],
  "summary": "string"
}

severity is one of block, nit, or info. The process aggregates the six passes

into a per-dimension verdict map plus two flattened lists — blockingFindings (every

block finding, tagged with its dimension) and nits (every nit finding, likewise

tagged) — and a joined summary. The review succeeds only when blockingFindings is

empty.

Related

[../../code-review/validator.js](../../code-review/validator.js) uses a different,

broader dimension set — quality, architecture, tests, security, ux, business

and materialises non-blocking findings as deferred debt on disk. This skill documents the

six-dimension rubric only; the two are not interchangeable.

想直接用这个技能?

本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。

它属于哪个仓库

星标★ 1,796
本站分层T1
该仓技能数2115
原文件路径library/specializations/collaboration/skills/six-dimension-code-review/SKILL.md

同一个仓库里的其他技能

看这个仓库的全部 2115 个技能