code-review

Review recent code changes and generate a prioritized security and quality report.

3|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Visma-Tech-LT/ai-workshop-marketplace --skill code-review-visma-tech-lt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Visma-Tech-LT/ai-workshop-marketplace/tree/main/plugins/sdw/skills/code-review
Command: npx skills add https://github.com/Visma-Tech-LT/ai-workshop-marketplace --skill code-review-visma-tech-lt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps prevent bad merges by reviewing recent code changes for security vulnerabilities, quality problems, correctness, and maintainability before you ship.

Core Features & Use Cases

  • Comprehensive security-focused review: Identifies potential security vulnerabilities and risky patterns that could introduce exploits.
  • Quality, correctness, and maintainability checks: Flags code smells, performance concerns, testing gaps, and compatibility issues that increase technical debt.
  • Actionable, prioritized feedback: Produces a structured report with concrete guidance, including critical issues to fix immediately.

Quick Start

Run the code-review skill to review recent changes and generate a review report in .claude/ai/review-YYYY-MM-DD-description.md.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review code changes for security vulnerabilities before a commit?▼

A pre-commit code review validates recent changes by checking for security vulnerabilities, code smells, and performance issues before merging. It flags risky patterns and correctness problems, producing a prioritized report that identifies critical issues to fix immediately.

How do I check test coverage and maintainability issues in a pull request?▼

Check test coverage and maintainability by running a review that flags testing gaps, code smells, and compatibility issues alongside security and performance concerns. It produces a structured report with actionable, prioritized findings to reduce technical debt before merging.

Does automated code review work with pull-request-style development cycles?▼

Yes, automated code review fits pull-request-style development cycles by validating recent code changes through tests and checks before committing. It produces a self-contained report covering security, quality, performance, test coverage, and compatibility with actionable findings.

What is the best way to catch quality and security issues before merging code?▼

The best way to catch quality and security issues before merging is to run a comprehensive review that identifies vulnerabilities, code smells, and performance concerns in recent changes. It outputs a prioritized report with concrete guidance on critical fixes to prevent bad merges.

How do I generate a code review report for recent changes?▼

Generate a code review report by running the review over recent changes, which produces a self-contained markdown file at .claude/ai/review-YYYY-MM-DD-description.md. The report covers security, quality, performance, test coverage, and compatibility with actionable, prioritized findings.