code-review

Review code for correctness, standards, tests, security, and maintainability.

1|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/MartinNevlaha/stratus-v2 --skill code-review-martinnevlaha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/MartinNevlaha/stratus-v2/tree/main/cmd/stratus/skills/code-review
Command: npx skills add https://github.com/MartinNevlaha/stratus-v2 --skill code-review-martinnevlaha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of reviewing code for correctness, adherence to project standards, security vulnerabilities, and maintainability, ensuring a higher quality codebase.

Core Features & Use Cases

  • Comprehensive Review: Checks code against multiple dimensions including correctness, project standards, tests, security, maintainability, and governance.
  • Structured Feedback: Provides a clear PASS/FAIL verdict with categorized issues (must_fix, should_fix, suggestion).
  • Use Case: Integrate this Skill into your CI/CD pipeline to automatically flag potential issues before merging code, saving developer time and reducing bugs.

Quick Start

Use the code-review skill to review the changes in the current branch for correctness and security.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code review for correctness and security in my CI/CD pipeline?

Automating code review in a CI/CD pipeline involves checking changes against multiple dimensions including correctness, security, and maintainability. This process flags potential issues before merging code, ensuring a higher quality codebase and saving developer time.

What is a structured code review and how does it produce a PASS/FAIL verdict?

A structured code review evaluates code across dimensions like project standards, tests, and governance. It identifies and categorizes issues with specific file and line number references, producing a clear PASS/FAIL verdict based on project-specific rules.

Can I use automated code review to enforce project-specific governance documents and standards?

Yes, automated code review can enforce project-specific standards. It requires adherence to rules defined in your governance documents, checking the codebase against these project standards to ensure compliance and maintainability.

What is the best way to categorize code review issues into must_fix, should_fix, and suggestions?

The best way to categorize code review issues is through a structured feedback system that classifies findings into must_fix, should_fix, and suggestion categories. This approach prioritizes security vulnerabilities and correctness issues alongside general maintainability improvements.

Does automated code review require predefined governance documents to check project standards?

Yes, automated code review requires predefined governance documents. The process relies on project-specific rules and standards defined within these documents to accurately evaluate code adherence and generate a PASS/FAIL verdict.