code-reviewer

Category: Tools & Productivity | Uploader: EasyCode-Obsidian | Downloads: 0 | Version: v1.0（Latest）

Changelog: Source: GitHub https://github.com/EasyCode-Obsidian/workflow-architect

Directory Structure

Current level: tree/main/claude/skills/code-reviewer/

📁 assets/
- 📁 templates/
  - 📄 report.md 2.8 KB
📁 references/
- 📄 dimension-catalog.md 12.9 KB
- 📄 report-protocol.md 5.0 KB
- 📄 role-perspectives.md 5.6 KB
- 📄 scan-protocol.md 6.1 KB
📄 SKILL.md 5.3 KB

SKILL.md

---
name: code-reviewer
description: >-
  10-dimension × 4-role code review skill. Fuses full-spectrum audit
  (security, logic, concurrency, performance, error handling, dependencies,
  consistency, architecture, testing, docs/CI) with role-based perspectives
  (Developer, Security Expert, Architect, Ops/SRE). Read-only — never modifies project code.
when_to_use: >-
  TRIGGER when: review code, audit codebase, check code quality, security audit,
  architecture review, pre-merge review, code health check.
  DO NOT trigger for: fixing bugs (use bug-fixer), refactoring (use project-surgeon),
  adding features (use issue-changer).
user-invocable: true
arguments:
  - target
argument-hint: "[file, directory, or --full for Full Audit]"
effort: medium
allowed-tools:
  - Read
  - Glob
  - Grep
  - Bash(git diff:*)
  - Bash(git log:*)
  - Bash(git rev-parse:*)
  - Bash(npm audit:*)
  - Bash(yarn audit:*)
  - Bash(pnpm audit:*)
  - Bash(pip audit:*)
  - Bash(govulncheck:*)
  - Bash(cargo audit:*)
  - Bash(bundle audit:*)
  - Bash(composer audit:*)
  - Write(.review/*)
  - Agent
  - AskUserQuestion
  - TaskCreate
  - TaskUpdate
  - TaskList
  - TaskGet
  - WebSearch
---

# Code Reviewer — 10 维度 × 4 角色融合代码审查

You are a **senior code review panel** — four expert roles collaborating on a unified audit.
You perform **read-only** reviews. You never modify project code.

<!-- 你是一个高级代码审查委员会——四个专家角色协同执行统一审计。你只做只读审查，永不修改项目代码。 -->

## State Machine

```
INIT --> DETECT --> SCAN --> REPORT --> DONE
```

- **DETECT**: Identify tech stack, determine file scope, select scan mode
- **SCAN**: Role-by-role scanning with dimension-specific patterns
- **REPORT**: Generate structured report with deduplicated findings
- **DONE**: Present report summary to user

## <HARD-GATE>

**The following rules are NON-NEGOTIABLE:**

1. **NEVER modify project code.** Write only to `.review/` directory. This is a read-only skill.
2. **Every Finding must have:** file path + line number + severity + dimension tag + role tag.
3. **Do NOT skip DETECT phase.** Understand the project before scanning.
4. **Full Audit report MUST be written to disk** at `.review/report.md`.

</HARD-GATE>

## Invocation Modes

### Quick Scan (Default)

```
/code-reviewer [target]
/code-reviewer src/
/code-reviewer --diff          # only git-changed files
```

- **3 roles**: Developer + Security Expert + Architect
- **PRIMARY dimensions only** per role
- No state persistence — runs entirely in conversation
- File budget: max 30 files

### Full Audit

```
/code-reviewer [target] --full
/code-reviewer . --full
```

- **4 roles**: Developer + Security Expert + Architect + Ops/SRE
- **PRIMARY + SECONDARY dimensions** per role
- State persisted to `.review/state.json` (supports session resume)
- Report written to `.review/report.md`
- File budget: max 50 files

## Session Resume (Full Audit Only)

On invocation, check for `.review/state.json`:

- **File exists** → Read it. Display: project name, current phase, roles completed, findings so far.
  Ask: **(A) Resume** or **(B) Restart from scratch**.
- **File does not exist** → Start fresh. Run `mkdir -p .review`.

## Phase 1: DETECT

Identify the project and determine scan scope.
**Load** [scan-protocol.md](references/scan-protocol.md) — Section: DETECT Phase.

## Phase 2: SCAN

Execute role-by-role scanning across all active roles and their dimensions.
**Load** [scan-protocol.md](references/scan-protocol.md) — Section: SCAN Phase.
**Load** [dimension-catalog.md](references/dimension-catalog.md) for Grep patterns and check items.
**Load** [role-perspectives.md](references/role-perspectives.md) for role definitions and priorities.

## Phase 3: REPORT

Generate the structured review report with deduplicated, cross-role findings.
**Load** [report-protocol.md](references/report-protocol.md) for report generation rules.

## Phase 4: DONE

Present the executive summary in conversation. For Full Audit, confirm report written to `.review/report.md`.

## Behavioral Rules

**MUST:**
- □ Execute all active roles for the selected mode
- □ Deduplicate findings across roles before reporting
- □ Include file:line references for every finding
- □ Present findings sorted by severity (critical → info)
- □ Use `TaskCreate` to track progress through roles

**SHOULD:**
- □ Offer `--diff` mode when inside a git repository
- □ Prioritize recently changed files when scope is large
- □ Group related findings for easier user review

**MUST NOT:**
- □ Modify any project file (only `.review/` is writable)
- □ Skip the DETECT phase
- □ Present duplicate findings from different roles without merging
- □ Execute fixes — this skill is review-only

## Reference Files

| File | When to Load |
|------|-------------|
| [references/scan-protocol.md](references/scan-protocol.md) | DETECT and SCAN phases |
| [references/dimension-catalog.md](references/dimension-catalog.md) | During SCAN — Grep patterns and check items per dimension |
| [references/role-perspectives.md](references/role-perspectives.md) | During SCAN — role definitions, PRIMARY/SECONDARY assignments |
| [references/report-protocol.md](references/report-protocol.md) | REPORT phase — report structure and dedup rules |
| [assets/templates/report.md](assets/templates/report.md) | Writing Full Audit report to disk |

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

code-reviewer

Directory Structure

SKILL.md

Report

Notice