code-review

Review Git repository code changes for security and correctness defects.

Updated Feb 9, 2025
One-click install
npx skills add https://github.com/obada-jaras/nextboost-starter --skill code-review-obada-jaras
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/obada-jaras/nextboost-starter/tree/main/.cursor/skills/code-review
Command: npx skills add https://github.com/obada-jaras/nextboost-starter --skill code-review-obada-jaras

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps identify and fix critical defects in code changes, prioritizing security, correctness, and regressions to improve code quality and reduce bugs.

Core Features & Use Cases

  • Automated Code Auditing: Analyzes code diffs to find security vulnerabilities, logic errors, and potential regressions.
  • Prioritized Findings: Classifies issues by severity (CRITICAL, HIGH, MEDIUM, LOW) and provides concrete evidence and fixes.
  • Use Case: Before merging a pull request, use this Skill to automatically scan the changes for any security flaws or critical bugs, ensuring only high-quality code enters the main branch.

Quick Start

Use the code-review skill to audit the current changes in the repository.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I audit code changes for security vulnerabilities and bugs before merging a pull request?

To audit code changes for security vulnerabilities and bugs, this Skill analyzes Git repository diffs to identify high-impact defects. It prioritizes security, correctness, and regressions, providing concrete evidence and automatic fixes based on severity classifications before pull request merging.

What is the difference between static analysis and an automated code review for pull requests?

An automated code review targets high-impact defects in changed Git files, prioritizing security and correctness over style. Unlike general static analysis, it uses a profile-based approach for different code domains and supports automatic fixing of identified issues based on severity.

Can I automatically fix detected security flaws and regressions found during a code review?

Yes, you can automatically fix detected security flaws and regressions. The Skill classifies identified issues by severity (CRITICAL, HIGH, MEDIUM, LOW) and supports automatic fixing of these defects based on their assigned severity level.

Does the code review auditing process work with all Git repository changes?

The code review auditing process works by analyzing changed files within a Git repository. It leverages a profile-based approach to evaluate different code domains, ensuring the detection of logic errors, regressions, and security vulnerabilities across the generated diffs.

When should I use an automated code audit instead of manual code review?

You should use an automated code audit when you need to quickly identify high-impact defects and security flaws in code diffs before merging. This approach prioritizes security, correctness, and regressions, supplying concrete evidence and severity classifications to streamline the pull request process.