skills.rest
mu-zhi
mu-zhiCOMMUNITY
Explore all skills by this author →
GitHub

change-review

Analyze code and documentation changes to identify delivery risks.

Updated Aug 27, 2026
Search Tags:#documentation#regression#risk-assessment#code-review#contract-drift#change-review
One-click install
npx skills add https://github.com/mu-zhi/CaliberHub --skill change-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: change-review
Source: https://github.com/mu-zhi/CaliberHub/tree/main/ai/skills/change-review
Command: npx skills add https://github.com/mu-zhi/CaliberHub --skill change-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only review of code and docs changes to surface delivery risks, including regressions, contract drift, and documentation gaps.

Core Features & Use Cases

  • Determine review scope from the current diff, changed files, or user-specified files.
  • Check four core areas: regression risk, contract drift between implementation and exposed behavior, missing verification or missing tests, and missing documentation or sync fallout.
  • If the change touches controllers, DTOs, or API behavior, verify whether API docs output (OpenAPI) should also reflect the update.
  • If the change affects frontend navigation, layout, or business copy, consult relevant docs before concluding.

Quick Start

Provide the current diff or the list of changed files to the skill and ask it to return prioritized findings.

Frequently Asked Questions about change-review

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

FAQPage Schema
How do I spot regression risks and contract drift in a code diff?▼

To spot regression risks and contract drift in a code diff, analyze the changes to surface mismatches between implementation and exposed behavior, returning prioritized findings with file and line references.

What is the best way to review pull requests for missing tests and documentation gaps?▼

The best way to review pull requests for missing tests and documentation gaps is analyzing changed files to identify missing verifications and documentation sync fallout, prioritizing findings by severity with specific file references.

How do I check if API documentation needs updates after changing controllers or DTOs?▼

To check if API documentation needs updates after changing controllers or DTOs, analyze the diff to verify whether OpenAPI output should reflect the updated API behavior and flag missing documentation as a risk.

Can I review specific user-specified files for delivery risks instead of the full diff?▼

Yes, you can review user-specified files for delivery risks by providing the file list to analyze, which surfaces regression risks, contract drift, and missing verifications ordered by severity with line references.

Does code review for frontend navigation changes require consulting business copy documentation?▼

Yes, code review for frontend navigation changes requires consulting relevant documentation and business copy before concluding, ensuring documentation gaps and sync fallout are identified during the change analysis.

What types of delivery risks are surfaced when analyzing commits and PRs?▼

Analyzing commits and PRs surfaces delivery risks including regression potential, contract drift between implementation and exposed behavior, missing verification or tests, and missing documentation or sync fallout.

Related Skills

Explore More Software Engineering Skills→
reedomreedom

collect-commits-and-files

Collect and categorize changed files from Git for review workflows.

Community
Advanced
KotlinKotlin
14

spring-kotlin-code-review

Analyze Kotlin and Spring changes for behavioral and operational risks.

Official
Intermediate
Dev10x-GuruDev10x-Guru
7

Dev10x:qa-scope

Analyze Pull Requests for QA risks and generate test cases.

Official
Advanced
dhntdhnt

code-review

Review pull request diffs and report evidence-backed findings by severity.

Official
Intermediate