Matrix Code Review

Review files, staged diffs, and pull requests for code issues.

110|9|Updated Dec 16, 2025
One-click install
npx skills add https://github.com/ojowwalker77/Claude-Matrix --skill matrix-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Matrix Code Review
Source: https://github.com/ojowwalker77/Claude-Matrix/tree/main/skills/review
Command: npx skills add https://github.com/ojowwalker77/Claude-Matrix --skill matrix-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Matrix Code Review eliminates noisy, shallow reviews by providing a structured, context-aware, multi-agent analysis that surfaces security, runtime, breaking, logic, and hygiene issues with minimized false positives.

Core Features & Use Cases

  • Five-agent orchestration: Orchestrator, Detection, Impact, Triage, Remediation, and Verification agents collaborate to produce prioritized findings.
  • Blast radius & dependency analysis: Transitive caller graph and test coverage analysis identify impacted files and service boundaries.
  • Hygiene (nuke) scans and verification: Detect dead code, circular deps, unused imports, console.log leftovers and run build/test/lint steps for final validation.
  • Use Case: Run on a staged diff or PR to get tiered findings, suggested fixes, regression risk assessments, and verification results before merging.

Quick Start

Ask Matrix to review staged changes by invoking /matrix:review staged for a comprehensive, context-aware code review.

Frequently Asked Questions about Matrix Code Review

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

FAQPage Schema
How do I perform a comprehensive code review on staged changes or pull requests?

Comprehensive code review on staged changes or pull requests is performed by running multi-agent analysis to detect security, runtime, breaking, logic, and hygiene issues. Invoke /matrix:review staged to receive prioritized findings, remediation suggestions, and automated verification results.

How does blast radius analysis work for evaluating pull request impact?

Blast radius analysis evaluates pull request impact by computing transitive caller graphs and test coverage to identify impacted files and service boundaries. This context-aware dependency analysis minimizes false positives and surfaces regression risks across the repository before merging.

Can I automatically detect dead code and unused imports during a code review?

You can automatically detect dead code, unused imports, circular dependencies, and console.log leftovers during a code review by running hygiene scans. These nuke scans are integrated into the review process alongside build, test, and lint verification steps for final validation.

What is the best way to get remediation suggestions and regression risk assessments before merging?

The best way to get remediation suggestions and regression risk assessments before merging is to apply context-aware code review to staged diffs or PR numbers. Multi-agent orchestration produces tiered findings with suggested fixes and automated verification results.

Does automated code review work with file paths and individual staged diffs across a repository?

Automated code review works with file paths, individual staged diffs, and PR numbers across a repository. It applies code indexing, taint tracing, and Context7 documentation lookups to analyze changes and produce prioritized, actionable findings.

Why does context-aware code review minimize false positives compared to shallow automated scans?

Context-aware code review minimizes false positives compared to shallow automated scans by using multi-agent orchestration and transitive dependency analysis. Structured detection, impact, triage, and remediation agents collaborate to validate issues against actual code context and service boundaries.