skills.rest
mDevsLabs
mDevsLabsCOMMUNITY
Explore all skills by this author →
Website𝕏@mDevsLabsGitHub

review-checklist

Guide code reviews with a checklist for common PR issues.

1|Updated May 20, 2026
Search Tags:#checklist#security#review#diff#i18n#pr#code
One-click install
npx skills add https://github.com/mDevsLabs/mAI --skill review-checklist-mdevslabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-checklist
Source: https://github.com/mDevsLabs/mAI/tree/main/.agents/skills/review-checklist
Command: npx skills add https://github.com/mDevsLabs/mAI --skill review-checklist-mdevslabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized, reusable checklist to guide code reviews, ensuring consistency and catching common issues early.

Core Features & Use Cases

  • Structured review prompts cover correctness, security, testing, i18n, routing, reuse, and cloud-impact checks.
  • PR and diff assessment during pull requests, diffs, or branch reviews to identify leftovers, unsafe patterns, or drift with UI imports.
  • Operational guidance helps teams maintain code quality across projects and enforce best practices.

Quick Start

Review a PR using this checklist to verify correctness, security, i18n, routing, and cloud-impact considerations.

Frequently Asked Questions about review-checklist

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

FAQPage Schema
What should a code review checklist for PRs cover?▼

A code review checklist for PRs should cover correctness, security, testing, i18n, routing, reuse, database, and cloud-impact areas. It helps detect console leftovers, missing returns, secrets exposure, and UI import inconsistencies during pull request diff assessments.

How do I check for secrets exposure and i18n gaps during a pull request review?▼

To check for secrets exposure and i18n gaps during a pull request review, apply a standardized checklist to the diff. This verifies unsafe patterns, missing translations, and routing drift to ensure codebase safety and maintainability.

Can I use a standardized checklist to detect desktop router drift and console leftovers?▼

Yes, you can use a standardized checklist to detect desktop router drift and console leftovers. Applying it during branch changes identifies these common issues alongside UI import inconsistencies, ensuring operational code quality across projects.

Does this code review checklist require any specific dependencies or components?▼

No, this code review checklist requires no specific dependencies or components. It serves as a standalone guide to help developers and teams enforce best practices and maintain code quality across various projects without additional setup.

What is the best way to verify cloud-impact and database considerations in a diff?▼

The best way to verify cloud-impact and database considerations in a diff is to codify these checks into your review workflow. A structured checklist ensures safe, maintainable code by systematically assessing operational impacts during pull requests.

Related Skills

Explore More Software Engineering Skills→
hamzaPixlhamzaPixl
2

cross-review

Run dual-model code reviews on pull request diffs and match findings by file and line.

Community
Advanced
garethrhughesgarethrhughes
5

infosec

Audit staged changes for security, privacy, and compliance violations before merge.

Community
Advanced
zajcazajca
2

go-linting

Configure golangci-lint with recommended Go linters for static analysis.

Community
Basic
skeletorfletskeletorflet
7

vulnerability-scanner

Analyze dependencies, secrets, and code patterns to generate prioritized vulnerability reports.

Community
Advanced