mvt-review

Review code changes for defects, standards, architecture, and test coverage.

19|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/uoyoCsharp/My-Virtual-TechTeam --skill mvt-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mvt-review
Source: https://github.com/uoyoCsharp/My-Virtual-TechTeam/tree/main/.claude/skills/mvt-review
Command: npx skills add https://github.com/uoyoCsharp/My-Virtual-TechTeam --skill mvt-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams perform structured code reviews that go beyond surface-level comments, so quality issues, architectural violations, missing tests, and risky edge cases are caught before code is merged.

Core Features & Use Cases

  • Severity-based review findings: Classifies issues as Critical, Warning, or Suggestion so teams can quickly decide whether to block, revise, or approve a change.
  • Multi-axis code review: Evaluates architecture, code quality, error handling, edge cases, tests, and security with optional aspect-focused review modes.
  • Workflow-aware review: Uses project context, design artifacts, implementation records, and change history to produce reviews that align with documented standards rather than isolated file comments.
  • Use Case: Review a feature branch before merge to verify it follows intended layer boundaries, handles failures correctly, avoids regressions, and has enough test coverage for the changed business logic.

Quick Start

Ask the AI to run mvt-review on your changed files or specify an aspect such as security, tests, or architecture for a focused review.

Frequently Asked Questions about mvt-review

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

FAQPage Schema
How do I perform a structured code review before a merge?

Catch merge-blocking issues by loading project context, resolving review targets from git diff, and evaluating architecture, quality, error handling, edge cases, tests, and security to classify defects by severity.

What is aspect-focused code review for pull requests?

Aspect-focused code review evaluates specific dimensions of a pull request, such as security, test coverage, or architectural drift, rather than scanning the entire diff, to target specific quality assurance goals.

How do I check test coverage and architectural drift in a feature branch?

Check test coverage and architectural drift in a feature branch by validating changed business logic against design artifacts and project context to verify layer boundaries and identify missing tests.

Can I review a specific file or aspect without scanning the entire git diff?

Yes, you can perform file-specific inspection or aspect-focused checks without scanning the entire git diff by specifying a single file or targeting a specific aspect like security or architecture for the review.

How does severity-based code review classification work?

Severity-based code review classification works by assigning findings as Critical, Warning, or Suggestion, allowing teams to quickly decide whether to block a merge, request revisions, or approve the change.