reviewing-python

Review Python codebases adversarially and issue APPROVED or REJECTED verdicts.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/outcomeeng/claude --skill reviewing-python-outcomeeng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-python
Source: https://github.com/outcomeeng/claude/tree/main/plugins/python/skills/reviewing-python
Command: npx skills add https://github.com/outcomeeng/claude --skill reviewing-python-outcomeeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adversarial code review to uncover design flaws through deep code comprehension, not checkbox compliance.

Core Features & Use Cases

  • Systematic code comprehension to identify architectural and implementation weaknesses.
  • Enforce ADR/PDR-aligned review discipline and highlight actionable failures.
  • Use Case: When validating a Python project, submit it to the skill to obtain an evidence-backed APPROVED/REJECTED verdict after full comprehension.

Quick Start

Provide a thorough adversarial review of the Python codebase to surface design flaws beyond superficial checks.

Frequently Asked Questions about reviewing-python

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

FAQPage Schema
How do I perform an adversarial Python code review to find design flaws?

Adversarial Python code review systematically analyzes codebases to surface architectural and implementation weaknesses missed by automated checks. It enforces ADR/PDR governance and delivers evidence-backed APPROVED or REJECTED verdicts after deep code comprehension.

What is the difference between automated linting and deep code comprehension for Python projects?

Automated linting checks superficial syntax and style compliance, while deep code comprehension identifies complex architectural design flaws. Adversarial review goes beyond checkbox compliance to evaluate structural integrity against ADR/PDR governance standards.

Does this Python code review approach work with existing unit tests and linters?

Yes, this review process is designed for Python projects already utilizing unit tests and linters. It complements these tools by uncovering deeper design flaws that standard automated checks routinely miss.

How do I validate ADR and PDR compliance during a Python code review?

You validate ADR/PDR compliance by enforcing alignment with established architectural and product design records during review. The process highlights actionable failures and outputs an evidence-based APPROVED or REJECTED verdict.

When should I use adversarial code review instead of standard code quality checks?

Use adversarial code review when automated code-quality checks are insufficient and you need to uncover hidden architectural flaws. It is necessary for rigorous gating and safety-aware review practices in complex Python projects.

Can I get an automated APPROVED or REJECTED verdict for my Python project?

Yes, submitting your Python project to this adversarial review process yields an evidence-backed APPROVED or REJECTED verdict. It evaluates the codebase against ADR/PDR governance and safety-aware review practices.