skills.rest
mercurjs
mercurjsOFFICIAL
Explore all skills by this author →
Website𝕏@mercurjsGitHub

code-review

Review mercur package code changes for contract integrity and type safety.

1.7k|421|Updated Apr 23, 2024
Search Tags:#automation#quality assurance#static analysis#code review#review checklist#mercur
One-click install
npx skills add https://github.com/mercurjs/mercur --skill code-review-mercurjs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/mercurjs/mercur/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/mercurjs/mercur --skill code-review-mercurjs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the process of reviewing code quality, ensuring contract compliance, and identifying potential issues before integration.

Core Features & Use Cases

  • Structured Checklist: Guides the reviewer through API, type safety, registry, UI, database, and documentation assessments.
  • Severity Categorization: Classifies issues into blocker, should fix, and suggestions for prioritized fixing.
  • Use Case: A developer submits a pull request; the reviewer uses this Skill to systematically check for contract deviations and safety issues to maintain code quality standards.

Quick Start

Use the code-review skill to evaluate recent changes in the repository's core package.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I structure a code review to catch contract deviations and type safety issues?▼

Structure a code review using a checklist that systematically assesses API contracts, type safety, registry, UI, database, and documentation to identify deviations and safety issues before integration.

What is the best way to categorize code review findings for prioritized fixing?▼

Categorize code review findings by severity into blockers, should fix items, and suggestions to prioritize fixing and maintain code quality standards during pull request evaluations.

Does static analysis help with evaluating contract integrity in pull requests?▼

Static analysis helps evaluate contract integrity by systematically checking code changes against established API contracts and type safety rules before merging packages into the main repository.

Can I use a review checklist to automate quality assurance for mercur packages?▼

You can use a structured review checklist to guide quality assurance for mercur packages, focusing on contract integrity, type safety, and best practices to reduce errors.

When do I need a structured code review process instead of ad hoc checking?▼

You need a structured code review process when evaluating complex package changes where contract compliance, database integrity, and type safety must be systematically verified to prevent integration errors.

Related Skills

Explore More Software Engineering Skills→
adrien-barretadrien-barret
8

budget-forecast

Forecast monthly cloud costs from Terraform, CloudFormation, Kubernetes, and Pulumi definitions.

Community
Advanced
heyallencaoheyallencao
118

ks-verify

Run automated test suites and coverage checks to validate code claims.

Community
Intermediate
bigeasyfreemanbigeasyfreeman
2

ldd-enforcement

Automate linting and syntax checking before testing in TDD workflows.

Community
Intermediate
flutterflutter
2.8k

dart-fix-runtime-errors

Identify and resolve Dart static analysis errors and runtime exceptions.

Official
Intermediate