code-reviewer

Identify security vulnerabilities, architectural issues, and contract changes in code diffs.

10|1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/spumer/i-m-senior-developer --skill code-reviewer-spumer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/spumer/i-m-senior-developer/tree/main/plugins/sdlc/skills/code-reviewer
Command: npx skills add https://github.com/spumer/i-m-senior-developer --skill code-reviewer-spumer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers identify and report security vulnerabilities, architectural issues, and contract changes in code diffs, enabling safer and more reliable software evolution.

Core Features & Use Cases

  • System-wide review of diffs for security, reliability, and contract adherence.
  • Loads security references and stack-specific guidelines to tailor checks per language and framework.
  • Produces a structured review report with file:line evidence and suggested remediation directions.

Quick Start

Run the reviewer on the current diff to generate a structured report.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I review code diffs for security vulnerabilities and architectural issues?

To review code diffs for security vulnerabilities and architectural issues, run an automated reviewer on your pull requests or patches to generate a structured report with file:line evidence and remediation directions.

Can I use static analysis to check Python and JavaScript pull requests for OWASP compliance?

Yes, you can use static analysis to check Python and JavaScript pull requests for OWASP compliance by loading stack-specific guidelines and security references to tailor checks per language and framework.

What is automated code review and how does it identify contract changes in patches?

Automated code review is the process of scanning code diffs to identify contract changes, security vulnerabilities, and architectural issues, outputting a structured report with file:line references for each finding.

Does automated code review work with continuous integration pipelines?

Automated code review works with continuous integration pipelines by analyzing diffs from pull requests or patches across Python and JS stacks, loading security references dynamically to produce structured review reports.

What is the best way to generate a structured security review report from a code diff?

The best way to generate a structured security review report from a code diff is to run an automated reviewer that applies OWASP and static analysis checks, producing file:line references and remediation directions.

How do I detect architectural issues and contract changes in my current diff?

To detect architectural issues and contract changes in your current diff, run an automated reviewer that performs system-wide analysis of patches, producing a structured report with specific file:line evidence.