project-review

Review repository changes for architecture consistency and regression risk.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/zhuangfanupup/modular-rag-mcp-server --skill project-review-zhuangfanupup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-review
Source: https://github.com/zhuangfanupup/modular-rag-mcp-server/tree/main/.github/skills/project-review
Command: npx skills add https://github.com/zhuangfanupup/modular-rag-mcp-server --skill project-review-zhuangfanupup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps reviewers quickly assess repository changes for architecture consistency, stability risks, configuration assumptions, and testing gaps, so teams can catch high-impact issues before release.

Core Features & Use Cases

  • Architecture Review: Checks layering, cross-module coupling, and hidden dependencies.
  • Critical Path Review: Focuses on ingestion, retrieval, and MCP tool behavior where failures matter most.
  • Quality Review: Evaluates test coverage, observability, and graceful degradation when dependencies fail.
  • Use Case: Use it when a pull request touches core server logic and you need a concise risk assessment with evidence-backed findings and minimal-change fixes.

Quick Start

Ask this skill to review the repository for architecture consistency, critical-path stability, configuration assumptions, and test coverage, then return prioritized findings with evidence and minimal fix suggestions.

Frequently Asked Questions about project-review

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

FAQPage Schema
How do I review pull request changes for architecture consistency and regression risk?

To review pull request changes for architecture consistency and regression risk, assess layering, cross-module coupling, and configuration assumptions. Focus on critical paths like ingestion, retrieval, and MCP tool behavior to ensure stability before release.

What is the best way to analyze change impact on critical-path stability in repository code?

Analyzing change impact on critical-path stability requires reviewing repository changes in ingestion, retrieval, and MCP tool behavior. Evaluate test coverage, observability, and graceful degradation to identify high-impact failures where they matter most.

How do I identify hidden dependencies and cross-module coupling during a code review?

To identify hidden dependencies and cross-module coupling during a code review, evaluate architectural layering across the repository. Check for configuration assumptions and regression risks to surface evidence-backed findings with severity prioritization.

Does code review for MCP tools require checking test coverage and graceful degradation?

Code review for MCP tools requires checking test coverage, observability, and graceful degradation when dependencies fail. Evaluate critical-path stability and configuration assumptions to catch high-impact issues before shipping repository changes.

How to generate minimal-change repair recommendations for repository risks found during review?

To generate minimal-change repair recommendations for repository risks, prioritize evidence-backed findings by severity. Focus on architectural consistency, critical-path stability, and testing gaps to provide concise, actionable fix suggestions.

Why should I use risk analysis for repository changes instead of standard code review?

Risk analysis for repository changes targets architecture consistency, critical-path stability, and configuration assumptions beyond standard code review. It prioritizes evidence-backed findings and minimal-change fixes to catch high-impact issues before release.