Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Python DBMigrator – Static AST Database Migration Auditor

    1

    Detects hidden schema traps, type mismatches, and silent query breakers before migrating SQLite to PostgreSQL. Returns strict JSON.

    $9.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Python DBMigrator – Static AST Database Migration Auditor

    Python DBMigrator – Static AST Database Migration Auditor

    Example session with this skill installed

    Run DBMigrator on the live/ directory to audit our migration schemas before switching to PostgreSQL.

    • Read your context and instructions
    • Compiled the python dbmigrator

    🔍 ARCHITECTURAL COMPLIANCE SECURED. ENFORCING DATABASE MIGRATION AUDIT BLUEPRINT ONLY.

    --- INPUT — live/scan1.sql ---
    -- Live run 1: clean PostgreSQL-compatible schema. No SQLite-specific constructs.

    CREATE TABLE users (
    id BIGINT GENERATED ALWAYS AS IDENTITY PRIMARY KEY,
    username VARCHAR(255) NOT NULL,
    is_active BOOLEAN NOT NULL DEFAULT TRUE,
    created_at TIMESTAMPTZ NOT NULL DEFAULT NOW()
    );

    CREATE TABLE orders (
    id BIGINT GENERATED ALWAYS AS IDENTITY PRIMARY KEY,
    amount NUMERIC(12, 2) NOT NULL,
    user_id BIGINT NOT NULL REFERENCES users(id)
    );

    --- INPUT — live/scan2.sql ---
    -- Live run 2: SQLite-specific schema. Multiple silent breakers.

    CREATE TABLE users (
    id INTEGER PRIMARY KEY AUTOINCREMENT,
    username VARCHAR(255),
    is_active INTEGER,
    created_at TEXT,
    notes CLOB
    );

    CREATE TABLE orders (
    id INTEGER PRIMARY KEY AUTOINCREMENT,
    amount REAL,
    user_id INTEGER

    );
    
    PRAGMA journal_mode = WAL;
    

    --- AUDIT OUTPUT ---

    {
      "audit_status": "CRITICAL",
      "findings": [
        {
          "id": "f1",
          "file": "live/scan2.sql",
          "line": 4,
          "severity": "HIGH",
          "signature": "SQLITE_AUTOINCREMENT",
    
      "message": "AUTOINCREMENT is not valid in PostgreSQL",
      "snippet": "id INTEGER PRIMARY KEY AUTOINCREMENT"
    
        },
        {
          "id": "f2",
          "file": "live/scan2.sql",
          "line": 6,
          "severity": "MEDIUM",
          "signature": "SQLITE_BOOL_AS_INT",
    
      "message": "Boolean column declared as INTEGER",
      "snippet": "is_active INTEGER"
    
        },
        {
          "id": "f3",
          "file": "live/scan2.sql",
          "line": 7,
          "severity": "HIGH",
          "signature": "SQLITE_DATE_AS_TEXT",
    
      "message": "Date column stored as TEXT",
      "snippet": "created_at TEXT"
    
        },
        {
          "id": "f4",
          "file": "live/scan2.sql",
          "line": 8,
          "severity": "HIGH",
          "signature": "SQLITE_DYNAMIC_TYPING",
    
      "message": "CLOB has no direct PostgreSQL equivalent",
      "snippet": "notes CLOB"
    
        },
        {
          "id": "f5",
          "file": "live/scan2.sql",
          "line": 12,
          "severity": "HIGH",
          "signature": "SQLITE_AUTOINCREMENT",
    
      "message": "AUTOINCREMENT is not valid in PostgreSQL",
      "snippet": "id INTEGER PRIMARY KEY AUTOINCREMENT"
    
        },
        {
          "id": "f6",
          "file": "live/scan2.sql",
          "line": 17,
          "severity": "MEDIUM",
          "signature": "SQLITE_PRAGMA",
    
      "message": "PRAGMA statement is SQLite-specific",
      "snippet": "PRAGMA journal_mode = WAL;"
    
        }
      ],
      "metadata": {
        "version": "1.2.0",
        "timestamp": "2026-10-16T11:57:00Z",
        "files_scanned": 2,
        "calls_found": 6
      }
    }
    

    --- VALIDATOR ---
    PASS: live/live_run_report.json
    Live run: PASS — 2 files scanned, 6 structural defects isolated.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Stop burning engineering hours on broken production cutovers and silent database failures. Python DBMigrator is a static AST-driven schema auditor built to transform verbose human migration checks into deterministic, machine-readable specifications optimized for LLM attention tracking. When development teams migrate lightweight application backends, AI agents repeatedly claim the migration scripts run perfectly. Then, text-based timestamps vanish, case-sensitive searches shrink, and auto-incrementing constraints break down inside the live environment. This engine flags structural database layout flaws without executing a single live query or risking data corruption. ## Core Capabilities - **Schema Constraint Auditing:** Instantly isolates SQLite-specific `AUTOINCREMENT` and `PRAGMA` layouts that generate deployment fatal errors under PostgreSQL. - **Silent Query Breach Prevention:** Identifies implicit case-sensitive `LIKE` operators and mismatched `?` parameter placeholders that cause database queries to return empty sets after cutover. - **Type-Mapping Integrity Auditing:** Flags dynamic types (`CLOB`, integers acting as booleans, strings holding date objects) that pass migration checks but trigger application errors in runtime. - **Automated Pipeline Verification:** Emits a schema-validated, flat JSON payload optimized for Git pre-commit hooks, infrastructure pipelines, and automated CI/CD code review gates. - **100% Local & Air-Gapped Operations:** Functions entirely offline with zero external network access and zero risk of corporate database telemetry or credentials leakage. ## When to use - Auditing production microservices, Telegram bots, or internal tools prior to staging a PostgreSQL migration. - Reviewing automated database migration structures generated by AI coding agents like Cursor or Claude Code. - Verifying legacy application repositories for hidden SQLite query dependencies before infrastructure updates. ## When NOT to use - Live row-by-row data streaming operations or generating active pgloader configuration trees. - Database platforms outside the native SQLite to PostgreSQL migration matrix setup. - General text generation, documentation formatting, or creative tasks meant exclusively for human consumption.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Code Quality & Review.

    Static AST graph analysis constraints only. Inspects source code syntax and relational schema definitions without local environment code execution or staging database deployment. Late imports inside dynamic runtime blocks are bypassed. The utility evaluates structural rules and does not validate active server variables or query buffer states.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 29 days ago

    Software
    Python

    Permissions

    Read Files

    File Scopes

    **/*.sql
    **/*.py
    **/*.js
    **/*.ts

    Read access scans SQL schema files and application code for SQLite-specific constructs that break on PostgreSQL migration. No files are written — the skill is advisory and returns a strict JSON report. No database connection is made. No code is executed.

    Listed1 month ago
    Updated29 days ago

    What's inside

    Frequently Asked Questions

    No, and that is by design to protect your production environment. DBMigrator is a specialized static analysis auditor. It scans your SQLite schema and application code to catch hidden architectural landmines before you migrate. It flags issues like case-sensitive LIKE queries or TEXT-based dates that look fine in SQLite but will completely crash a production PostgreSQL environment.

    No, DBMigrator operates on a 100% Secure, Zero-Trust model. It is a strictly read-only auditor that identifies risks without asking for your database credentials, moving rows, or risking data corruption. Instead, you get a clean, actionable JSON report with exact line numbers and severity levels to execute a flawless, zero-downtime manual migration or script update.

    It provides comprehensive cross-language coverage. DBMigrator scans raw .sql schema files alongside your application backend code written in Python, JavaScript, and TypeScript. It instantly catches dangerous database-specific patterns like ? placeholders or last_insert_rowid() calls embedded inside your app logic.

    Because a successful script execution doesn't mean your app won't crash under production load. SQLite is highly forgiving with types, while PostgreSQL is notoriously strict. DBMigrator catches "silent production breakers" — like hidden AUTOINCREMENT patterns or 0/1 boolean interpretations — that PostgreSQL will reject at runtime, saving your team days of painful emergency debugging and system downtime.

    You get immediate, production-ready access to the full DBMigrator skill. This includes the complete advanced engine for detecting SQLite-specific PRAGMAs, hidden type-mapping violations, and implicit query mismatches. Every single check is verified against a rigorous 12-point automated test protocol to ensure your code is enterprise-grade and ready for Postgres.

    New in Code Quality & Review