skills.rest
OzeroHAX
OzeroHAXCOMMUNITY
Explore all skills by this author →
GitHub

review-code-checklist

Run P0 and P1 quality checks on code changes before merging.

32|7|Updated Jan 28, 2026
Search Tags:#testing#code review#checklist#security#merge#quality gate
One-click install
npx skills add https://github.com/OzeroHAX/AssistAgents --skill review-code-checklist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-code-checklist
Source: https://github.com/OzeroHAX/AssistAgents/tree/main/templates/skills/review/code/checklist
Command: npx skills add https://github.com/OzeroHAX/AssistAgents --skill review-code-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized, quick quality gate for code reviews, ensuring essential checks are performed before merging code.

Core Features & Use Cases

  • Standardized Checks: Enforces a consistent set of P0 and P1 checks for functional correctness, security, tests, maintainability, documentation, and performance.
  • Streamlined Reviews: Helps teams quickly identify critical issues and non-blocking findings, speeding up the merge process.
  • Use Case: A developer finishes a feature and wants a quick pre-merge check to ensure it meets the basic quality standards before submitting it for a more thorough review.

Quick Start

Run the review-code-checklist skill to perform a quality gate check on the provided code changes.

Frequently Asked Questions about review-code-checklist

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

FAQPage Schema
What is a pre-merge code review checklist?▼

It serves as a rapid quality gate that verifies code changes against defined P0 and P1 criteria for functional correctness, security, test coverage, and performance before merging.

How do I run a quick quality gate check on my code before submitting a pull request?▼

Run the review-code-checklist skill on your code changes to perform a rapid quality gate check. It identifies critical P0 issues and non-blocking P1 findings to speed up the merge process.

What criteria are checked during a pre-merge code review?▼

Pre-merge code reviews check functional correctness, security, test coverage, maintainability, documentation, and performance against defined P0 and P1 criteria to ensure merge readiness.

Can I merge code if some review checklist findings are non-blocking?▼

Yes, you can merge code if all P0 checks are met. Remaining P1 findings are considered non-blocking for release, allowing the merge process to proceed without delay.

Does a checklist-based code review replace a thorough manual code review?▼

No, it serves as a quick pre-merge check for basic standards. Developers use it to ensure code meets essential quality criteria before submitting it for a more thorough review.

Related Skills

Explore More Software Engineering Skills→
KaiserWhoLearnsKaiserWhoLearns

find-bugs

Analyze local branch diffs for bugs, security vulnerabilities, and code quality issues.

Community
Advanced
SSiertsemaSSiertsema

quality-gate-definition

Define and enforce quality gates across CI/CD pipeline stages.

Community
Advanced
IngrammlIngramml

Testing Workflow

Detect the testing framework, run tests, and report results with coverage.

Community
Intermediate
SuperlendSuperlend

cairo-vulnerability-scanner

Detect six vulnerability patterns in Cairo and StarkNet smart contracts.

Official
Advanced