lc:check-foreign-keys

To check Laravel migrations for missing foreign key constraints, you can analyze your codebase to cross-reference database migration definitions with Eloquent model relationship methods, detecting orphaned relationships and schema discrepancies.

Eloquent model relationships cause data integrity issues when they lack corresponding database-level foreign key constraints, allowing orphaned records and runtime errors due to misaligned onDelete configurations and missing schema rules.

You can find orphaned relationships and invalid onDelete configurations by scanning your entire Laravel project to cross-reference Eloquent relationship definitions against migration files, identifying missing constraints and incorrect cascade actions.

Yes, you can automatically generate migration files and suggest model updates to align your database schema with your Eloquent definitions, resolving missing foreign keys and invalid onDelete actions detected during the codebase analysis.

You should validate database schema integrity during a Laravel refactor to ensure every belongsTo relationship in your models is backed by a corresponding foreign key constraint, preventing runtime errors and maintaining data consistency.