code-review

Provide a structured checklist for code reviews to identify bugs, logic errors, security vulnerabilities, memory leaks, and asynchronous issues.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/rensjaspers/agents --skill code-review-rensjaspers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/rensjaspers/agents/tree/main/skills/code-review
Command: npx skills add https://github.com/rensjaspers/agents --skill code-review-rensjaspers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps prevent bugs and security vulnerabilities by providing a focused checklist for code reviews, ensuring critical issues are not overlooked.

Core Features & Use Cases

  • Bug Prevention: Identifies potential crashes, logic errors, security flaws, memory leaks, and asynchronous issues.
  • Focused Review: Ignores stylistic preferences to concentrate on functional correctness and safety.
  • Use Case: When reviewing a pull request, use this Skill to ensure the changes do not introduce regressions or security risks before merging.

Quick Start

Use the code-review skill to review the attached code changes for potential bugs.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I check my code for security vulnerabilities before a pull request?

To check code for security vulnerabilities before a pull request, use a structured code review checklist to identify critical defects, logic errors, and memory leaks. This ensures changes do not introduce regressions or risks before merging.

What is the best way to prevent bugs and memory leaks during code reviews?

The best way to prevent bugs and memory leaks during code reviews is to apply a focused checklist that targets functional correctness and safety, specifically identifying potential crashes and asynchronous issues while ignoring style preferences.

Does this code review checklist focus on functional defects or formatting?

This code review checklist focuses exclusively on functional correctness and critical defects, intentionally ignoring stylistic preferences and formatting to concentrate on preventing logic errors, security flaws, and memory leaks.

Can I use a structured checklist to audit general code changes for regressions?

Yes, you can use a structured code review checklist to audit general code changes for regressions. It is applicable during pull request reviews and general code audits to identify potential crashes and safety issues.

How do I identify asynchronous issues when reviewing code changes?

To identify asynchronous issues when reviewing code changes, apply a focused code review checklist that specifically targets asynchronous behavior alongside memory leaks, security vulnerabilities, and logic errors to prevent critical defects.