Skip to content

jaktestowac/awesome-copilot-for-testers / plugins/code-review-advanced/skills/code-review-advanced

code-review-advanced

Verified

Performs evidence-driven code review for pull requests, legacy modules, and quality-critical changes. Use when reviewing complex or multi-file changes, test automation suites, architectural refactors, or hot paths that need analysis of correctness, maintainability, security, performance, test quality, and operability risks. Provides structured feedback with severity-ranked findings, actionable recommendations, and clear rationale. For a fast sanity check of a small diff or single file, use the code-review skill instead.

resources/review-report-template.md

View on GitHub
# Advanced Code Review Report Template

Use this template for high-signal review output.
Replace placeholders and remove sections that are clearly not relevant, but keep the overall structure.

## Review Metadata

- **Scope:** `<PR / files / module / repository>`
- **Review goal:** `<correctness / architecture / readiness / security / test quality / mixed>`
- **Change type:** `<feature / bug fix / refactor / migration / test-only / infra>`
- **Assumptions / missing context:** `<list any gaps explicitly>`

## Executive Summary

`<2-5 sentences explaining what changed, what looks solid, and the overall risk profile.>`

## Recommendation

**Status:** `<approve / comment / request changes>`

**Why:**

- `<main reason 1>`
- `<main reason 2>`
- `<main reason 3>`

## What Looks Strong

- `<strength worth preserving>`
- `<good engineering decision>`
- `<useful test / design / operational choice>`

## Findings Overview

| Severity | Area            | Summary           | Evidence                       | Suggested action         |
| -------- | --------------- | ----------------- | ------------------------------ | ------------------------ |
| High     | Testing         | `<short finding>` | `<file / behavior / omission>` | `<smallest safe action>` |
| Medium   | Maintainability | `<short finding>` | `<file / behavior / omission>` | `<smallest safe action>` |

## Detailed Findings

### 1. `<Finding title>`

- **Severity:** `<Blocker / High / Medium / Low / Note>`
- **Area:** `<correctness / architecture / security / performance / testing / maintainability / operability>`
- **Evidence:** `<what in the code or diff supports this>`
- **Risk:** `<why this matters>`
- **Recommendation:** `<smallest safe improvement>`

### 2. `<Finding title>`

- **Severity:** `<Blocker / High / Medium / Low / Note>`
- **Area:** `<area>`
- **Evidence:** `<evidence>`
- **Risk:** `<risk>`
- **Recommendation:** `<recommendation>`

## Missing or Weak Coverage

- `<missing test scenario>`
- `<missing operational safeguard>`
- `<missing docs, migration notes, or failure diagnostics>`

## Follow-up Suggestions

- `<nice-to-have improvement>`
- `<longer-term design idea>`
- `<risk reduction step that does not block merge>`
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall