npx claudepluginhub ojowwalker77/claude-matrix --plugin matrixWant just this skill?
Then install: npx claudepluginhub u/[userId]/[slug]
This skill should be used when the user asks to "review this code", "review PR", "code review", "review staged changes", "blast radius analysis", "check impact of changes", or needs comprehensive context-aware code review.
This skill is limited to using the following tools:
references/agents/detection.mdreferences/agents/impact.mdreferences/agents/remediation.mdreferences/agents/triage.mdreferences/agents/verification.mdreferences/review-phases.mdMatrix Code Review
Perform comprehensive, context-aware code review using 5-agent architecture with 95% false positive reduction.
Tip: This skill runs in a forked context for an unbiased perspective - similar to how a human reviewer would approach the code for the first time.
Architecture
ORCHESTRATOR (parses target, routes, aggregates)
│
├── DETECTION AGENT → security, runtime, breaking, logic flaws, hygiene (nuke)
├── IMPACT AGENT → blast radius, transitive graph, test coverage
├── TRIAGE AGENT → tier assignment, confidence calibration, noise filter
├── REMEDIATION AGENT → context-aware fixes, regression checks
└── VERIFICATION AGENT → build, test, lint validation
Usage
Parse user arguments from the skill invocation (text after the trigger phrase).
Expected format: <target> [mode]
- target: File path, PR number, or "staged" for staged changes
- mode (optional):
default|lazy(default: from config ordefault)
Modes
Default Mode (Comprehensive)
Full 5-agent review pipeline with maximum index utilization:
- Detection: Security vulns, runtime issues, breaking changes, hygiene (nuke scan)
- Impact: Transitive blast radius (2-3 levels), service boundaries, test coverage
- Triage: Tier classification, >80% signal ratio target
- Remediation: Context-aware fixes matching codebase patterns
- Verification: Run build, test, lint commands automatically
Lazy Mode (Quick)
Detection agent only:
- Direct code inspection
- Critical issues only (Tier 1)
- ~2-3 comments, no blast radius
Review Pipeline
Follow the 5-agent orchestration detailed in references/review-phases.md:
- Orchestrator - Parse target, dispatch agents, aggregate results
- Detection Agent - Find security, runtime, breaking, logic issues
- Impact Agent - Calculate transitive blast radius, test coverage
- Triage Agent - Classify tiers, calibrate confidence, filter noise
- Remediation Agent - Generate fixes, check regression risk
- Verification Agent - Run build, test, lint; report results
Early exit: If Detection finds nothing critical, skip Impact/Triage depth.
Examples
/matrix:review src/utils/auth.ts # Default mode (comprehensive)
/matrix:review staged # Review staged changes
/matrix:review staged lazy # Quick review of staged changes
/matrix:review 123 # Review PR #123
/matrix:review 123 lazy # Quick review of PR #123
Additional Resources
Reference Files
references/review-phases.md- Orchestrator + 5-agent pipelinereferences/agents/detection.md- Detection patterns and output formatreferences/agents/impact.md- Blast radius algorithmreferences/agents/triage.md- Tier classification and signal ratioreferences/agents/remediation.md- Fix generation and regression checksreferences/agents/verification.md- Build/test/lint command detection and execution
Similar Skills
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.