Review Mercur package code changes for contract compliance, type safety, and regression risk.
npx skills add https://github.com/OZVE/cuarta-avenida --skill code-review-ozve
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
Reviews code changes for contract compliance, type safety, and regression risk to prevent regressions and ensure reliable software across Mercur packages.
Review a PR by applying the code-review skill to the changed files to generate a structured risk and compliance report.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
Fandry96Analyze code diffs to identify security vulnerabilities and produce structured findings.
mercurjsReview mercur package code changes for contract integrity and type safety.
burgebjOrchestrate multi-model code reviews before merging pull requests.
eykdReview GitHub pull requests for correctness, style, test coverage, and standards.
