code-review-checklist

Apply a code-review checklist across pull requests and patch submissions.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/marablemarcel/Living-Lytics --skill code-review-checklist-marablemarcel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-checklist
Source: https://github.com/marablemarcel/Living-Lytics/tree/main/living-lytics/.agent/skills/code-review-checklist
Command: npx skills add https://github.com/marablemarcel/Living-Lytics --skill code-review-checklist-marablemarcel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide provides a structured set of code-review guidelines to improve software quality, security, and maintainability.

Core Features & Use Cases

  • Comprehensive checklists covering correctness, security, performance, and code quality.
  • Clear anti-patterns and best-practice recommendations to streamline reviews.
  • Guidance for reviewers to provide actionable feedback and maintain consistency across teams.

Quick Start

Review a pull request by applying the checklist to assess correctness, security, performance, and maintainability.

Frequently Asked Questions about code-review-checklist

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

FAQPage Schema
What should a code review checklist cover to improve software quality and security?

A code review checklist for pull requests should evaluate correctness, security, performance, and maintainability. It enforces review guidelines, flags anti-patterns, and documents findings to guide actionable fixes across diverse languages and architectures.

How do I use a code review checklist for pull request and patch submissions?

Apply the checklist to pull request and patch submissions to assess correctness, security, performance, and maintainability. Enforce rubric criteria, document findings, and flag anti-patterns to guide actionable fixes during the review process.

Can I apply the same code review guidelines across different programming languages and architectures?

Yes, the code review guidelines apply across diverse languages and architectures. The rubric focuses on universal criteria including correctness, security, performance, and maintainability, enforcing best practices regardless of the specific programming language.

How do I flag anti-patterns and missing documentation during a code review?

Identify anti-patterns and missing documentation by applying the review rubric to the code submission. Document these findings alongside security and performance issues to guide the author toward actionable fixes and maintain team consistency.

What is the best way to provide actionable code review feedback?

Provide actionable code review feedback by documenting findings based on a structured checklist. Enforce criteria for correctness and security, flag anti-patterns, and reference best-practice recommendations to guide specific, clear fixes for the author.