python-code-review

Reviews Python code against PEP 8 and Google Style Guide standards.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/rishikksh20/nexus-code-agent --skill python-code-review-rishikksh20
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: python-code-review
Source: https://github.com/rishikksh20/nexus-code-agent/tree/main/.agents/skills/python-code-review
Command: npx skills add https://github.com/rishikksh20/nexus-code-agent --skill python-code-review-rishikksh20

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually auditing Python code for style violations, security flaws, and maintainability issues is slow and inconsistent. This Skill provides a systematic review checklist covering PEP 8, the Google Python Style Guide, security, and performance so every review follows the same rigorous standard. ## Core Features & Use Cases - Standards-Based Review: Checks style, imports, naming, docstrings, and type hints against PEP 8, PEP 257, PEP 484, and the Google Python Style Guide. - Security & Performance Audits: Detects SQL injection risks, hardcoded secrets, unsafe functions like eval(), mutable default arguments, and quadratic string concatenation. - Structured Findings Report: Produces severity-ranked issues with line numbers, code excerpts, recommended fixes, and rationale. - Use Case: Before merging a pull request, ask for a review of the changed Python files and receive a prioritized list of critical security issues, style violations, and quick-win improvements. ## Quick Start Review the Python file I just edited for PEP 8 compliance, security issues, and maintainability problems.

Frequently Asked Questions about python-code-review

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

FAQPage Schema
How do I review Python code for PEP 8 compliance?▼

Run a structured review checking line length, indentation, imports, naming conventions, and whitespace rules against PEP 8. This Skill walks through each category systematically and reports violations with line numbers and corrected code examples.

What is the difference between PEP 8 and Google Python Style Guide?▼

PEP 8 is Python's official style guide covering formatting and naming basics. The Google Python Style Guide builds on it with stricter rules for docstrings, type hints, imports, and practices like avoiding mutable default arguments and staticmethods.

How do I check Python code for security vulnerabilities?▼

Look for SQL injection via string-formatted queries, hardcoded credentials, unsafe calls like eval() and exec(), and unsafe deserialization with pickle or yaml.load(). The review flags each issue with severity and a parameterized or safer alternative.

Which linters enforce PEP 8 and Google style automatically?▼

pylint with Google's pylintrc configuration provides comprehensive linting, while Black or Pyink handle auto-formatting. Complement them with pytype or mypy for type checking and isort for import ordering.

When is it acceptable to violate PEP 8 rules?▼

Consistency within a project takes priority over rigid rule adherence. Violations are acceptable when following the rule reduces readability, when matching surrounding legacy code, or when compliance would break backwards compatibility.