code-review-advanced

Reviews pull requests and refactors with severity-ranked findings across correctness, security, and test quality.

113|17|Updated Oct 5, 2025
One-click install
npx skills add https://github.com/jaktestowac/awesome-copilot-for-testers --skill code-review-advanced-jaktestowac
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-advanced
Source: https://github.com/jaktestowac/awesome-copilot-for-testers/tree/main/plugins/code-review-advanced/skills/code-review-advanced
Command: npx skills add https://github.com/jaktestowac/awesome-copilot-for-testers --skill code-review-advanced-jaktestowac

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Shallow code reviews often miss real engineering risks like hidden regressions, weak test assertions, architectural boundary violations, and security gaps. This Skill performs evidence-driven, multi-lens reviews of complex pull requests, legacy modules, and test automation suites, producing structured findings with severity, evidence, risk, and actionable recommendations. ## Core Features & Use Cases - Multi-Lens Review Workflow: A five-phase process covering framing, context analysis, inspection across seven dimensions (correctness, maintainability, architecture, security, performance, testing, operability), structured findings, and a final recommendation. - Severity-Ranked Findings: Every finding includes severity (Blocker/High/Medium/Low/Note), evidence, risk, and the smallest safe recommended fix, ending with an approve/comment/request-changes verdict. - Test Automation Lens: A dedicated checklist for reviewing test suites, covering flakiness, assertion quality, test isolation, page object design, selectors, and CI diagnostics. - Use Case: A reviewer receives a multi-file PR adding login tests with hard waits and weak negative-path assertions. The Skill produces a report flagging the flakiness risk as High severity, citing the exact evidence, and recommending deterministic wait conditions before merge. ## Quick Start Ask the AI to critically review this pull request for correctness, security, and test quality risks using the advanced code review skill.

Frequently Asked Questions about code-review-advanced

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a large pull request for hidden risks?▼

Use a multi-phase review that first frames scope and change type, then inspects correctness, architecture, security, performance, and testing dimensions. Each finding should carry severity, concrete evidence, risk, and a recommended fix rather than style opinions.

What should a code review checklist cover beyond style?▼

A thorough checklist covers correctness, maintainability, architecture, security and privacy, performance, testing quality, and operability. High-signal red flags include branching without tests, swallowed errors, cross-layer imports, and secrets in logs or fixtures.

How do I review test automation code for flakiness?▼

Check for hard waits instead of deterministic signals, shared state between tests, weak assertions that only check element presence, and missing CI failure artifacts. A test that passes unreliably is a feedback-system defect, not a minor issue.

When should I use a quick review instead of an advanced review?▼

Use a lightweight review for small diffs or single files needing a fast sanity check. Reserve the advanced multi-lens review for large pull requests, legacy audits, refactors, and changes touching critical boundaries like auth or persistence.

How should severity levels be assigned in code review findings?▼

Use Blocker for likely wrong or unsafe changes, High for significant regression or security risk, Medium for important quality issues, Low for non-urgent improvements, and Note for observations. Avoid inflating severity so blockers stay meaningful.