review-python-service

Review Python FastAPI and SQLAlchemy changes for fintech compliance and correctness.

1|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/sswapnil2/ai-config-fintech --skill review-python-service
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-python-service
Source: https://github.com/sswapnil2/ai-config-fintech/tree/main/skills/review-python-service
Command: npx skills add https://github.com/sswapnil2/ai-config-fintech --skill review-python-service

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review a Python backend change in a fintech service for correctness, type discipline, async pitfalls, and fintech rules (PII, idempotency, audit, money-as-Decimal).

Core Features & Use Cases

  • Enforces monetary value handling with Decimal and proper quantization.
  • Checks for strict typing, async correctness, and safe SQLAlchemy usage.
  • Scales across FastAPI services in fintech contexts, ensuring auditability and idempotency.

Quick Start

Review the latest PR against the Python fintech service to identify issues.

Frequently Asked Questions about review-python-service

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

FAQPage Schema
How do I review a FastAPI backend for fintech compliance and correctness?

To review a FastAPI backend for fintech compliance, you need to audit Python changes for type discipline, async correctness, and safe SQLAlchemy usage. This ensures monetary values use Decimal quantization, idempotency, and audit logging are correctly implemented.

Why does my Python fintech service require Decimal for money handling?

Python fintech services require Decimal for money handling to prevent floating-point rounding errors in financial calculations. Enforcing Decimal quantization during backend reviews ensures strict monetary correctness and compliance in SQLAlchemy data models.

What is async correctness in FastAPI and SQLAlchemy fintech services?

Async correctness in FastAPI and SQLAlchemy fintech services means avoiding blocking operations within async endpoints and ensuring safe database session management. Reviewing these aspects prevents race conditions and maintains data integrity during concurrent financial transactions.

How do I check for idempotency and audit logging in Python backend changes?

To check for idempotency and audit logging in Python backend changes, review database migration integrity and logging safety. This ensures financial transactions are safely repeatable without duplication and compliance trails are securely maintained.

Can I use this Python review process for non-fintech FastAPI applications?

You can use this Python review process for non-fintech FastAPI applications to enforce strict typing and async correctness. However, its specific checks for Decimal money handling, idempotency, and audit trails are specialized for fintech compliance contexts.

What are the limitations of automated Python backend compliance reviews?

Limitations of automated Python backend compliance reviews include focusing strictly on code-level correctness, typing discipline, and migration integrity. They may not fully capture complex business logic flaws or external regulatory changes without explicit rule updates.