code-review-cleanup-agent

Analyze code diffs for bugs, security vulnerabilities, and maintainability issues.

2|1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/gil-kapel/cursor-course-2026 --skill code-review-cleanup-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-cleanup-agent
Source: https://github.com/gil-kapel/cursor-course-2026/tree/main/course/he_course/module-02-skills-and-agents/lesson-2.10-code-review-agent/code-review-cleanup-agent
Command: npx skills add https://github.com/gil-kapel/cursor-course-2026 --skill code-review-cleanup-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers systematically review code changes for bugs, security issues, and maintainability concerns, improving code quality.

Core Features & Use Cases

  • Guided Review Process: Follows a structured interactive loop to identify key issues and ask relevant questions.
  • Comprehensive Analysis: Checks for logic errors, security vulnerabilities, missing tests, and cleanup opportunities.
  • Use Case: When reviewing a pull request or code update, use this Skill to ensure all critical aspects are examined thoroughly before merging.

Quick Start

Provide the diff of the updated code along with context, and ask for a detailed review focusing on security and correctness.

Frequently Asked Questions about code-review-cleanup-agent

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

FAQPage Schema
How do I review code changes for security vulnerabilities and bugs before deployment?

Review code changes by providing the updated diff along with context for a structured analysis. This process identifies logic errors, security vulnerabilities, regressions, and missing tests to ensure code correctness before merging.

What's the best way to check a pull request for maintainability issues and regressions?

Checking a pull request for maintainability issues requires a comprehensive analysis across multiple files, including code diffs and documentation. This structured review identifies critical risks, logic errors, and cleanup opportunities to improve overall code quality.

Does this code review process work with multiple files and documentation?

Yes, the code review process works across multiple files such as code diffs and documentation. It analyzes these inputs comprehensively to identify critical risks, missing tests, and maintainability issues before deployment.

How do I systematically analyze code diffs for logic errors and missing tests?

Systematically analyze code diffs by following a guided interactive loop that asks relevant questions and examines critical aspects. This structured approach checks for logic errors, security vulnerabilities, and cleanup opportunities thoroughly.

When do I need a structured code review for my codebase?

You need a structured code review when examining code updates or pull requests before merging. It ensures all critical aspects like security vulnerabilities, bugs, and maintainability concerns are reviewed thoroughly to prevent regressions.

Can I use this to ensure all critical aspects of a code update are examined before merging?

Yes, you can use this to ensure all critical aspects of a code update are examined thoroughly before merging. It follows a guided interactive process to identify bugs, security vulnerabilities, regressions, and maintainability issues.