code-reviewer

Name: code-reviewer
Availability: InStock
Author: U1PNS

Identify security, quality, and performance risks in codebases before merge.

8|2|Updated Jan 25, 2026

Search Tags:#security #code-quality #static-analysis #code-review #software-security #review-report

Ready to run

npx skills add https://github.com/u1pns/skills-entrepeneur --skill code-reviewer-u1pns

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/u1pns/skills-entrepeneur/tree/main/code-reviewer
Command: npx skills add https://github.com/u1pns/skills-entrepeneur --skill code-reviewer-u1pns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review often misses subtle security flaws, performance bottlenecks, and maintainability issues. This skill applies adversarial thinking and structured review techniques to catch vulnerabilities before merge, improving security posture and code quality.

Core Features & Use Cases

Adversarial thinking during code reviews to identify security holes, data leaks, and quality issues.
Static-analysis-like guidance for maintainability, performance, and best practices.
Use Case: When reviewing a feature PR, assess input validation, error handling, dependency safety, and edge-case behavior to prevent regressions.

Quick Start

Review the provided codebase or diff for security, performance, and quality issues and generate a professional 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 a pull request for security vulnerabilities and code quality issues?▼

Review a pull request for security vulnerabilities and code quality by applying adversarial thinking and static-analysis-like checks to input validation, error handling, and dependency safety. This approach catches subtle data leaks and performance bottlenecks before merge.

What is the best way to catch security flaws and performance bottlenecks in a codebase before merging?▼

The best way to catch security flaws and performance bottlenecks is to evaluate the codebase for edge-case behavior and input validation using structured review techniques. This process identifies maintainability issues and hardens software security posture before integration.

Does this code review approach work with standalone codebases across different programming languages?▼

Yes, this code review approach works with standalone codebases across different programming languages by assessing dependency safety, edge-case handling, and input validation. It applies language-agnostic structured techniques to produce actionable review reports.

How do I generate a structured report with actionable recommendations from a code diff?▼

Generate a structured report from a code diff by analyzing the changes for security holes, quality risks, and performance issues. The process produces evidence-based findings with actionable recommendations for resolving identified vulnerabilities.

Can I use static analysis to check dependency safety and edge-case behavior in my feature PR?▼

You can use static-analysis-like guidance to check dependency safety and edge-case behavior in your feature PR. This review mechanism assesses input validation and error handling to prevent regressions and identify potential security holes.

What are the limitations of using adversarial thinking for code reviews?▼

When using adversarial thinking for code reviews, limitations include the need for a provided codebase or diff to analyze, as it cannot assess missing code. It focuses on identifying input validation gaps and edge-case risks rather than automatically patching the detected vulnerabilities.