Individual skill

six-dimension-code-review

Structured pull-request review across six fixed dimensions — correctness, clarity, consistency, coverage, complexity, and change-scope — producing a per-dimension verdict plus severity-tagged findings. Use when reviewing a PR diff or running the collaboration PR lifecycles.

library/specializations/collaboration/skills/six-dimension-code-review/SKILL.md

Read pinned source

Source commit feb68abe397acc14f32b34984975c48fedba2b33

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Local scripts
Last checked
Nov 3, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,898
Repository last updated
Nov 1, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.