review-code

Review Python code against TDD, style, and typing constraints.

Updated Mar 2, 2022
One-click install
npx skills add https://github.com/ysuurme/azure_hello_world --skill review-code-ysuurme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-code
Source: https://github.com/ysuurme/azure_hello_world/tree/main/.agents/skills/review-code
Command: npx skills add https://github.com/ysuurme/azure_hello_world --skill review-code-ysuurme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents costly architectural drift and unreadable code changes by enforcing strict, review-time standards that keep implementations clear, testable, and maintainable.

Core Features & Use Cases

  • Scope-bound micro review: Focuses on syntax and file-level logic so macro architecture mapping is handled elsewhere.
  • TDD-gated approvals: Rejects logic changes that lack an initial failing test and corresponding test updates.
  • Cognitive-load reduction rules: Enforces shallow nesting, small functions, descriptive naming, and consistent type hints/PEP-8 style.
  • Standard-library first guidance: Encourages low supply-chain risk and consistent abstractions, with clear exceptions for external HTTP calls.

Quick Start

Use the review-code skill when you want an AI to review a pull request against TDD, indentation, naming, typing, and refactoring constraints, then return structured observations and required before/after fixes.

Frequently Asked Questions about review-code

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

FAQPage Schema
How do I enforce TDD and pytest standards during a Python code review?

To enforce TDD and pytest standards during a Python code review, the skill validates that logic changes include an initial failing test and corresponding test updates before returning structured approval observations.

What is architectural drift in Python and how do I prevent it in pull requests?

Architectural drift in Python is prevented in pull requests by applying review-time constraints that enforce shallow nesting, small functions, and standard-library first dependency selection to keep implementations maintainable.

How do I check Python code for PEP-8 style and typing requirements before approval?

You check Python code for PEP-8 style and typing requirements by running a scope-bound micro review that enforces strict indentation rules, descriptive naming, and consistent type hints.

Does this code review approach support refactoring legacy Python code?

Yes, this code review approach supports refactoring legacy Python code by validating the submission against cognitive-load reduction rules and TDD constraints to ensure clear, testable modifications.

When should I use a standard-library first dependency selection during Python development?

You should use a standard-library first dependency selection during Python development to maintain low supply-chain risk and consistent abstractions, except when handling external HTTP calls.

What are the limitations of micro-level code reviews for macro architecture mapping?

The limitation of micro-level code reviews for macro architecture mapping is that this approach focuses strictly on syntax and file-level logic, meaning broader architectural mapping must be handled elsewhere.