code-review

Name: code-review
Availability: InStock
Author: winsorllc

Execute linters, static analysis, and security scanners on code.

1|Updated Feb 25, 2026

Search Tags:#automation #git #static analysis #code review #linting #security

Ready to run

npx skills add https://github.com/winsorllc/upgraded-carnival --skill code-review-winsorllc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/winsorllc/upgraded-carnival/tree/main/.pi/skills/code-review
Command: npx skills add https://github.com/winsorllc/upgraded-carnival --skill code-review-winsorllc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of reviewing code for quality, security vulnerabilities, and adherence to standards, reducing manual effort and improving code integrity.

Core Features & Use Cases

Pre-commit Checks: Ensure code quality before committing using linters and formatters.
Static Analysis: Analyze code for bugs, complexity, and security flaws.
Security Scanning: Detect potential vulnerabilities and exposed secrets.
Use Case: Before merging a pull request, automatically run linters, security audits, and complexity checks to ensure the code meets project standards.

Quick Start

Run a comprehensive code review on the current project's staged changes.

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 checks for security vulnerabilities and bugs?▼

Automate code review by executing linters, static analysis tools, and security scanners to identify bugs, detect vulnerabilities, and ensure code quality before merging pull requests.

Can I run static analysis and security scanning on staged Git changes?▼

Yes, static analysis and security scanning can be applied to staged Git changes to analyze code for bugs, complexity, and exposed secrets before committing.

What is the best way to run pre-commit code quality checks using linters?▼

The best way to run pre-commit code quality checks is by automating linters and formatters within your software development workflow to enforce project standards automatically.

Do I need GitHub CLI to automate security audits for pull requests?▼

You need Git, npm, and potentially the GitHub CLI for comprehensive security audits and code checks to fully integrate automated reviews into your pull request workflow.

Why does automated code review reduce manual effort in software development?▼

Automated code review reduces manual effort by automatically executing linters and security scanners to check code integrity, ensuring adherence to standards without human intervention.

What are the limitations of using static analysis for detecting security flaws?▼

Static analysis limitations include requiring integration with Git, npm, and potentially GitHub CLI for comprehensive checks, as standalone analysis may not detect all runtime vulnerabilities.