checklist-code-review

Name: checklist-code-review
Availability: InStock
Author: akourmaz

Enforce a structured code-review checklist covering functionality, security, architecture, and style.

Updated Mar 2, 2026

Search Tags:#architecture #security #maintainability #style #quality #code-review

Ready to run

npx skills add https://github.com/akourmaz/translate2 --skill checklist-code-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: checklist-code-review
Source: https://github.com/akourmaz/translate2/tree/main/.agents/skills/checklist-code-review
Command: npx skills add https://github.com/akourmaz/translate2 --skill checklist-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Code Review Checklist formalizes the quality gates reviewers use after a coder submits changes, ensuring consistency and preventing regressions.

Core Features & Use Cases

Comprehensive categories covering Functionality, Security, Architecture, Code Quality, and Style.
Provides actionable Acceptance Criteria and a structured review flow to guide reviewers.
Useful for teams enforcing standardized reviews and rapid, safe merges.

Quick Start

Apply this checklist after every coder submission to ensure functional, secure, architectural, and stylistic criteria are met.

Frequently Asked Questions about checklist-code-review

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

FAQPage Schema

How do I enforce consistent code review standards before merging?▼

Enforce consistent code review standards by applying a structured checklist that gates merges based on functionality, security, architecture, maintainability, and style criteria. This prevents regressions and ensures consistent reviews across your team.

What categories should a comprehensive code review checklist cover?▼

A comprehensive code review checklist should cover Functionality, Security, Architecture, Code Quality, and Style. These categories ensure the codebase meets structured acceptance criteria and receives clear remediation steps.

How do I perform a structured post-submission code review?▼

Perform a post-submission code review by applying structured acceptance criteria and test guidance across the codebase. This verifies functionality and security while providing clear remediation steps for any failures.

Can I use a code review checklist to verify security and architecture constraints?▼

Yes, a code review checklist can verify security and architecture constraints. It implements structured acceptance criteria to gate quality, ensuring your codebase meets required security and architectural standards before merging.

What is the best way to provide actionable remediation steps during a code review?▼

The best way to provide actionable remediation steps is to use a structured review flow with predefined acceptance criteria. This guides reviewers to deliver clear, actionable feedback for rapid and safe merges.

When do I need a formalized quality gate for code submissions?▼

You need a formalized quality gate for code submissions when your team requires standardized reviews to prevent regressions. It ensures consistent, safe merges by verifying functional, secure, architectural, and stylistic criteria.