Code Review

Review code for logic errors, security vulnerabilities, and compliance gaps.

6|3|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/carson-sweet/sweetclaude --skill code-review-carson-sweet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Code Review
Source: https://github.com/carson-sweet/sweetclaude/tree/main/skills/code-review
Command: npx skills add https://github.com/carson-sweet/sweetclaude --skill code-review-carson-sweet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the challenge of maintaining high code quality and security standards by automating the review process across logic, security, compliance, and architectural domains.

Core Features & Use Cases

  • Multi-Domain Analysis: Performs targeted reviews for logic errors, security vulnerabilities (OWASP Top 10), and regulatory compliance.
  • Caucus Review: Employs five specialized agents to independently analyze code, synthesizing findings into a consensus-based report to minimize false positives.
  • Use Case: Before merging a large pull request, use this skill to perform a comprehensive security and compliance audit to ensure the changes meet internal standards and external regulatory requirements.

Quick Start

Invoke the code review skill to analyze the current staged changes for security vulnerabilities and logic errors.

Frequently Asked Questions about Code Review

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

FAQPage Schema
How do I automate a security and compliance audit for a pull request?

A multi-domain code review identifies logic errors, security vulnerabilities like the OWASP Top 10, and regulatory compliance gaps. It operates on staged changes, specific files, or pull requests using inline analysis or background agent dispatch.

How does a caucus review mechanism work for finding code vulnerabilities?

A caucus review deploys five specialized agents to independently analyze code, synthesizing their findings into a consensus-based report to minimize false positives during the security and compliance audit.

Can I use static analysis to check staged changes for regulatory compliance?

Yes, static analysis can check staged changes for regulatory compliance. The review requires integration with project-specific compliance context to accurately identify regulatory gaps before merging software changes.

What is the best way to review code for OWASP Top 10 vulnerabilities before merging?

The best way to review code for OWASP Top 10 vulnerabilities is to perform a multi-domain audit. This uses specialized agents to independently analyze your pull request and synthesize a consensus-based security report.

Do I need project-specific compliance context to run a software quality audit?

Yes, you need project-specific compliance context to run an effective software quality audit. The review process relies on this context and defined behavioral contracts to identify regulatory gaps and ensure consistent output.