code-review

Review Mercur package code changes for contract compliance, type safety, and regression risk.

Updated Apr 3, 2026

Search Tags:#type-safety #quality-assurance #code-review #pull-request #regression-risk #contract-compliance #mercur

Ready to run

npx skills add https://github.com/OZVE/cuarta-avenida --skill code-review-ozve

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/OZVE/cuarta-avenida/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/OZVE/cuarta-avenida --skill code-review-ozve

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reviews code changes for contract compliance, type safety, and regression risk to prevent regressions and ensure reliable software across Mercur packages.

Core Features & Use Cases

Contract checks: verify that public contracts and API boundaries remain stable.
Risk assessment: identify potential regressions and safety gaps in changes across packages.
Use Case: during PR reviews, run the code-review skill to generate a structured evaluation of changes before merging.

Quick Start

Review a PR by applying the code-review skill to the changed files to generate a structured risk and compliance report.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I review code changes for contract compliance and type safety?▼

To review code changes for contract compliance and type safety, apply the code-review skill to the modified files in your pull request. It evaluates API boundary stability and type safety, generating a structured findings report aligned with review-checklist rules.

When do I need to run a formal code review for regression risk?▼

You need to run a formal code review for regression risk during pull request reviews, after completing non-trivial implementations, or when cross-package changes require a formal quality assessment to prevent regressions.

Can I use this code review skill for cross-package changes in Mercur packages?▼

Yes, you can use this code review skill for cross-package changes in Mercur packages. It specifically applies to Mercur packages to verify public contracts remain stable and to identify potential regressions and safety gaps across packages.

What is the best way to assess API boundary stability before merging a pull request?▼

The best way to assess API boundary stability before merging is to run the code-review skill on the changed files. It performs contract checks to verify that public contracts and API boundaries remain stable and outputs a structured risk report.

What does the code review output report include?▼

The code review output report includes structured findings on contract compliance, type safety, and regression risk. It implements the checks described in the review checklist and provides a formal quality assessment of the code changes.

Does this code review tool require any specific dependencies to function?▼

No, this code review tool does not require any specific external dependencies to function. It operates independently to evaluate code changes and generate a structured findings report based on its internal review checklist.