python_review

Review Python code for language-dependent defects and system-level implementation risks beyond static diagnostics.

4|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/synthaicode/XRefKit --skill python-review-synthaicode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: python_review
Source: https://github.com/synthaicode/XRefKit/tree/main/skills/python_review
Command: npx skills add https://github.com/synthaicode/XRefKit --skill python-review-synthaicode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Static analyzers, linters, and type checkers miss runtime, framework, deployment, and business-intent defects in Python code. This Skill performs a structured review across categories like concurrency, resource lifetime, error handling, and schema resilience, explicitly separating what static analysis proved from what still needs runtime or human evidence. ## Core Features & Use Cases - Category-based review matrix: Covers static baseline, resource efficiency, operational resilience, synchronization, error handling, time/locale/encoding, state and determinism, contract and schema resilience, and traceability, with every category reporting pass, needs_confirmation, or not_applicable. - Static-analysis boundary table: Separates confirmed_by_static_analysis, not_detectable_by_static_analysis, and requires_runtime_or_human_evidence so reviewers know exactly what remains unverified. - Gate verdict and handoffs: Emits a blocked, needs-review, or proceed verdict with evidence, and routes security, trace-continuity, and design-assumption findings to the appropriate specialist Skills. - Use Case: Before merging a Python service change, run this Skill on the target package to get an evidence-backed findings list with severity and remediation, plus a pre-CI gate verdict. ## Quick Start Ask the AI to run the python_review Skill on a target path such as a package or service directory and return the findings matrix and gate verdict.

Frequently Asked Questions about python_review

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

FAQPage Schema
How do I review Python code beyond what linters and type checkers catch?▼

Run a structured category-based review that covers runtime behavior, concurrency, resource lifetime, error handling, and schema resilience. This Skill executes per-category checks, records what static analysis could not prove, and emits findings with severity, evidence, and remediation.

What kinds of Python defects does static analysis miss?▼

Static analysis typically cannot prove runtime wiring, deployment limits, framework behavior, business intent, or third-party API correctness. The review marks these as not_detectable_by_static_analysis or requires_runtime_or_human_evidence instead of silently passing them.

Can this review handle custom Python frameworks?▼

Yes, but custom framework behavior such as decorators, dependency injection, plugin discovery, and lifecycle hooks must be verified against local evidence first. The Skill never assumes public-framework semantics for custom frameworks without repository proof.

When should findings be handed off instead of fixed in the review?▼

Security-scope findings go to security_review, XDDP trace-continuity gaps go to qa_gate_review, implementation-local findings return to python_implementation_flow, and report wording needs route to review_report_composition. The review itself never expands into fixing or security analysis.

Why does a category show needs_confirmation instead of pass?▼

A category cannot pass merely because static analysis found no issue when it depends on runtime, deployment, lifecycle, or third-party behavior that was not verified. The missing evidence is named so a human or follow-up run can resolve it.