audit-code-reviewer

Merge findings from six parallel subagents into a comprehensive code review report.

2|1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/vosslab/vosslab-skills --skill audit-code-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-code-reviewer
Source: https://github.com/vosslab/vosslab-skills/tree/main/skills/audit-code-reviewer
Command: npx skills add https://github.com/vosslab/vosslab-skills --skill audit-code-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of conducting a thorough code review by engaging multiple independent reviewers, thereby improving code quality and reducing the risk of overlooked issues.

Core Features & Use Cases

  • Parallel Reviews: Concurrently launches six different subagents to review code from various angles.
  • Customizable Scopes: Each subagent focuses on a specific aspect of the code, such as testing, style, documentation, or legacy code.
  • Integrated Findings: Merges the findings from all subagents into a comprehensive review report.
  • Use Case: Ideal for teams looking to ensure that their codebase adheres to high standards before merging or releasing changes.

Quick Start

To initiate an audit of your code changes, simply run the command: /vosslab-skills:audit-code-reviewer

Frequently Asked Questions about audit-code-reviewer

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

FAQPage Schema
How do I automate code review with multiple independent reviewers?

Code review using parallel multi-reviewer audits works by concurrently launching independent subagents for parallel analysis. These subagents merge their distinct findings into a coherent review report to ensure code quality.

What is the best way to run parallel code reviews for different scopes like testing and documentation?

Running parallel code reviews for specific scopes is done by engaging customizable subagents. Each subagent independently focuses on a distinct aspect like testing, style, documentation, or legacy code before merging findings.

How do I conduct a comprehensive code review before merging changes?

Comprehensive code review before merging changes is conducted by executing various subagents with distinct review scopes. The system merges all findings into an integrated report to reduce the risk of overlooked issues.

Does parallel multi-reviewer code audit work for legacy code analysis?

Parallel multi-reviewer code audit works for legacy code analysis by assigning specific subagents to focus on legacy code scopes. The parallel processing mechanism concurrently analyzes code changes from multiple angles including legacy systems.

How many subagents are launched during a parallel code audit?

Six different subagents are launched during a parallel code audit. These subagents concurrently review code from various angles and merge their independent findings into a single comprehensive report.