debug-production

Name: debug-production
Availability: InStock
Author: Vulnetix

Compare production and local database schemas, migrations, and environment variables.

Updated Aug 27, 2026

Search Tags:#debugging #database #production #migrations #schema #environment variables

Ready to run

npx skills add https://github.com/Vulnetix/vdb-api --skill debug-production

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-production
Source: https://github.com/Vulnetix/vdb-api/tree/main/.claude/skills/debug-production
Command: npx skills add https://github.com/Vulnetix/vdb-api --skill debug-production

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you systematically identify and resolve bugs that manifest exclusively in the production environment, bridging the gap between local development and live deployment issues.

Core Features & Use Cases

Environment Comparison: Compares production database schemas, applied migrations, and environment variables against local configurations.
Targeted Debugging: Allows focusing investigation on specific tables, endpoints, or error messages.
Use Case: If a feature works perfectly in your local setup but crashes in production, this Skill provides the diagnostic steps to pinpoint the discrepancy, whether it's a schema drift, a missing migration, or a data type mismatch.

Quick Start

Use the debug-production skill to investigate issues related to the 'users' table.

Frequently Asked Questions about debug-production

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

FAQPage Schema

How do I debug issues that only happen in production but not locally?▼

Debug production-only issues by systematically comparing production database schemas, applied migrations, and environment variables against local configurations to pinpoint discrepancies like schema drift or missing migrations.

What causes a feature to work locally but crash in production?▼

Common causes include database schema drift, missing database indexes, BigInt timestamp or boolean type mismatches, case-sensitivity errors in raw SQL, or missing environment variables in the production environment.

How do I check for database schema drift between local and production environments?▼

Check for database schema drift by comparing the production database schema and applied migration status directly with your local environment to identify unapplied migrations or missing indexes.

Do I need production database credentials to debug a production-only issue?▼

Yes, you need access to production database credentials and logs to accurately compare production database schema, data integrity, and environment variables against your local setup.

Can I investigate a production crash by focusing on specific database tables?▼

Yes, targeted debugging allows you to focus your investigation on specific tables, endpoints, or error messages to efficiently identify data type mismatches or missing indexes.