skills.rest
PavkaBrika
PavkaBrikaCOMMUNITY
Explore all skills by this author →
GitHub

parallel-code-review

Coordinate four read-only subagents to review a code diff from security, performance, correctness, and readability perspectives.

1|Updated Jun 23, 2022
Search Tags:#performance#security#readability#multi-agent#parallel#code-review#merge-report
One-click install
npx skills add https://github.com/PavkaBrika/debtbookapp --skill parallel-code-review-pavkabrika
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: parallel-code-review
Source: https://github.com/PavkaBrika/debtbookapp/tree/main/.cursor/skills/parallel-core-review
Command: npx skills add https://github.com/PavkaBrika/debtbookapp --skill parallel-code-review-pavkabrika

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Four parallel read-only subagents review the same diff from distinct lenses (security, performance, correctness, readability) and their findings are merged into a single, prioritized report to accelerate high-quality PR reviews.

Core Features & Use Cases

  • Multi-lens reviews: four read-only subagents analyze the same changes from security, performance, correctness, and readability perspectives.
  • Unified reporting: results are merged into one consolidated report with prioritized findings.
  • Use Case: Ideal for large diffs or risky PRs where a comprehensive, parallel review catches issues that a single pass might miss.

Quick Start

Launch four parallel read-only subagents to review the diff and produce a merged findings report.

Frequently Asked Questions about parallel-code-review

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

FAQPage Schema
How do I run a parallel multi-agent code review for a large diff?▼

A parallel multi-agent code review launches four read-only subagents to analyze the same diff from security, performance, correctness, and readability perspectives, then merges their findings into a single prioritized report.

What is the best way to review risky PRs for security and performance issues?▼

Reviewing risky PRs through a multi-lens approach applies four parallel read-only subagents to assess security and performance alongside correctness and readability, producing a unified consolidated report of prioritized findings.

Can I use parallel subagents to catch code review issues that a single pass misses?▼

Yes, using parallel subagents to review code changes from distinct lenses ensures a comprehensive assessment that catches issues a single pass might miss, which is ideal for large diffs requiring high-quality analysis.

How does merging findings from multiple code review agents work?▼

Merging findings involves structured result aggregation from four parallel read-only subagents, consolidating their security, performance, correctness, and readability assessments into one prioritized merged findings report.

When do I need a four-way code review instead of a standard single pass?▼

You need a four-way code review when handling large diffs or risky PRs where a comprehensive, multi-faceted assessment is required before merging to ensure high-quality code review.

Related Skills

Explore More Software Engineering Skills→
tygwantygwan
1

quality-gate

Automate quality validation at pre-commit, pre-merge, pre-release, and post-release CI gates.

Community
Advanced
seshxnseshxn

swarm-code-review

Coordinate multi-lane code reviews by specialist agents and aggregate findings into a prioritized report.

Community
Advanced
birgitta410birgitta410
15

sensors_wrap-tool

Convert command-line tool output into sensors-cli JSON schema.

Community
Intermediate
alexanderguyalexanderguy
4

linear-issue-workflow

Transform a Linear issue into a planned, reviewed implementation workflow.

Community
Advanced