skills.rest
zhixuan312
zhixuan312COMMUNITY
Explore all skills by this author →
GitHub

mma-review

Automate parallel per-file code reviews for correctness, security, and quality.

5|4|Updated Apr 9, 2026
Search Tags:#security#quality#merge#parallel#review#diff#code
One-click install
npx skills add https://github.com/zhixuan312/multi-model-agent --skill mma-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mma-review
Source: https://github.com/zhixuan312/multi-model-agent/tree/main/packages/server/src/skills/mma-review
Command: npx skills add https://github.com/zhixuan312/multi-model-agent --skill mma-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides parallel, per-file code reviews to catch correctness, security, and quality issues before merging, reducing bottlenecks and integration risk.

Core Features & Use Cases

  • Independent per-file review: Each changed file is reviewed in parallel by a different model to surface issues quickly.
  • Cross-file ripple awareness: When a diff is provided, the reviewer identifies how changes in one file may impact others and merge readiness.
  • Focused governance: Supports targeted focus areas (e.g., correctness, security) to steer the review toward high-risk dimensions.

Quick Start

Submit a review task with the changed file paths or provided diff to start parallel per-file reviews.

Frequently Asked Questions about mma-review

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

FAQPage Schema
How do I run parallel code reviews on a multi-file diff before merging?▼

To run parallel code reviews, submit changed file paths or a diff to trigger independent per-file reviewers that identify correctness, security, and quality issues before merging.

Can I focus a code review on specific issues like security vulnerabilities?▼

Yes, you can provide an optional focus parameter such as security or correctness to steer parallel per-file code reviews toward targeted high-risk dimensions in your diff.

How does cross-file ripple detection work when reviewing a diff?▼

Cross-file ripple detection works by routing each changed file to an independent reviewer that analyzes the diff to identify how modifications in one file impact others and overall merge readiness.

What do I need to provide to start an automated per-file code review?▼

You need to provide a target containing file paths or a diff for the changed files, and you can optionally specify a review focus like correctness or security to guide the independent reviewers.

Is parallel per-file code review better than a single review for multi-file changes?▼

Parallel per-file code review differs by routing each file to an independent reviewer, reducing bottlenecks and integration risk by surfacing correctness and security issues quickly across multi-file changes.

What are the limitations of routing each file to an independent reviewer for code review?▼

Routing each file to an independent reviewer focuses on per-file correctness and security, but you should provide a diff if you need cross-file ripple detection to assess broader merge readiness.

Related Skills

Explore More Software Engineering Skills→
reedomreedom

collect-commits-and-files

Collect and categorize changed files from Git for review workflows.

Community
Advanced
gabriellpequenogabriellpequeno
8

code-review-checklist

Identify correctness, security, and maintainability issues in pull requests.

Community
Basic
anderson-0anderson-0
4

checkpoint-preview

Guide structured human review of code changes with diff inspection and review trails.

Community
Advanced
fyrsmithlabsfyrsmithlabs

research:orchestration

Coordinate parallel research agents and synthesize findings into a consolidated report.

Official
Advanced