code-review-checklist

Standardize pull request reviews with structured code, test, documentation, and security checklists.

Updated Sep 6, 2025
One-click install
npx skills add https://github.com/kabaka/oscar-export-analyzer --skill code-review-checklist-kabaka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-checklist
Source: https://github.com/kabaka/oscar-export-analyzer/tree/main/.github/skills/code-review-checklist
Command: npx skills add https://github.com/kabaka/oscar-export-analyzer --skill code-review-checklist-kabaka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often miss critical aspects leading to inconsistent quality and security gaps. This checklist standardizes the review process, ensuring consistency across PRs and faster, safer merges.

Core Features & Use Cases

  • Structured checks for quality, testing, documentation, and security.
  • Promotes cross-team consistency and on-boarding for new reviewers.
  • Use Case: When a PR is ready, guide the reviewer through essential criteria to avoid regressions.

Quick Start

Review every pull request against this checklist before merging to ensure quality, documentation, and security standards are met.

Frequently Asked Questions about code-review-checklist

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

FAQPage Schema
How do I standardize code reviews to stop missing security and quality gaps in pull requests?

To standardize code reviews, apply a structured pull request checklist that enforces criteria across code, tests, documentation, and security. This ensures consistent PR reviews, prevents regressions, and enables safer, faster merges across your development workflow.

What should a pull request checklist include to maintain coding standards?

A pull request checklist for coding standards should include structured checks for code quality, testing coverage, documentation completeness, and security vulnerabilities. Verifying these categories before merging prevents regressions and maintains cross-team consistency.

How do I onboard new developers to review pull requests consistently?

To onboard new developers to review pull requests consistently, provide a comprehensive code review checklist. This guides reviewers through essential criteria for quality, testing, documentation, and security, standardizing their assessments and ensuring safer merges.

Does a code review checklist work for OSCAR Export Analyzer development workflows?

Yes, this code review checklist applies directly to OSCAR Export Analyzer development workflows. It standardizes pull request evaluations by enforcing quality, testing, documentation, and security reviews specific to your development process.

Why does my pull request review process still result in inconsistent quality and security gaps?

Your pull request review process likely lacks a standardized checklist, causing inconsistent quality and security gaps. Applying a comprehensive review checklist across code, tests, documentation, and security ensures every PR meets essential criteria before merging.

Can I add reference assets to guide my code review checklist?

Yes, you can enrich your code review checklist by supporting optional reference assets. These assets provide additional guidance to help reviewers thoroughly evaluate code, tests, documentation, and security criteria within structured pull request reviews.