agentleFS
rioX432rioX432/agent-witness/.claude/skills/review/SKILL.md

review

Skill1 starsChanged 5 months agoApache-2.0View on GitHub

Multi-agent parallel code review against the base branch

192 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use close-spec, daily-arxiv and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dzhngSkill

    close-spec

    When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).

    Also in 5 projects that use this

  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新

    Also in 5 projects that use this

  • dzhngSkill

    design-with-images

    Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • +5 more from Lambenthan
  • +3 more from dzhng

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 156 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run each command individually — do NOT chain with &&

    line 26
  2. Very specific:

    Check .claude/agents/ for project-specific reviewer agents (e.g., kmp-reviewer, ui-reviewer).

    line 73
  3. Distinctive:

    Deduplicate: remove findings reported by multiple agents

    line 78

“Common” is measured: kept by at least 6 in 10 of the 156 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/review — Multi-Agent Code Review

Review the current branch's changes against the base branch using parallel review agents.

Step 0: Prepare

  1. Identify base branch (main or master) and current branch
  2. git log — commits on this branch
  3. git diff {base}...HEAD — full changeset
  4. gh pr view --json body — PR description (if available)
  5. Run each command individually — do NOT chain with &&

Step 1: Build Change Context

  1. Understand the intent from commit messages and PR description
  2. Categorize changed files: core logic, UI, infrastructure, tests
  3. Identify risk areas: complex changes, new integrations, security-sensitive code

Step 2: Multi-Agent Parallel Review

Launch two review agents in parallel (model: sonnet):

Agent A: Bug & Logic + Security

Review the changed files for bugs, logic errors, and security issues.
Read REVIEW.md (if exists) or .claude/rules/ for review criteria.

Focus areas:
- Null safety violations
- Concurrency issues
- Error handling gaps
- Security: hardcoded secrets, input sanitization, data exposure
- Platform compatibility
- Performance: memory leaks, main thread blocking, redundant calls

For each finding: [file:line] severity — description
Severity: Critical / Warning / Suggestion / Nit

Agent B: Architecture & Quality

Review the changed files for architecture and code quality.
Read REVIEW.md (if exists) or .claude/rules/ for review criteria.

Focus areas:
- Architecture: SRP, layer boundaries, dependency direction
- Design patterns: consistency with existing codebase
- Testing: changed code has corresponding test updates
- Naming and readability
- Unnecessary complexity or over-engineering

For each finding: [file:line] severity — description
Severity: Critical / Warning / Suggestion / Nit

Project-Specific Reviewers (if available)

Check .claude/agents/ for project-specific reviewer agents (e.g., kmp-reviewer, ui-reviewer). If found, launch them in parallel with Agents A and B.

Step 3: Merge Findings

  1. Collect findings from all agents
  2. Deduplicate: remove findings reported by multiple agents
  3. Assign final severity:
    • Critical: crash, data loss, security vulnerability, incorrect behavior
    • Warning: potential bug, performance issue, architecture violation
    • Suggestion: improvement opportunity, non-blocking
    • Nit: style/preference, optional

Step 4: Present Report

## Review Summary

**Branch:** {current} → {base}
**Files changed:** N
**Risk level:** Low / Medium / High
**Reviewed by:** Agent A (Bug/Security) + Agent B (Arch/Quality) + {project-specific}

### Critical (must fix)
- [file:line] description

### Warning (should fix)
- [file:line] description

### Suggestion (nice to have)
- [file:line] description

### Nit (optional)
- [file:line] description

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.