Menu
Ensures correct execution order of migrations, seeders, and tests in CI
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Defines DTO structure, lifecycle, and transformation rules across the application
Handles Filament multi-tenancy: tenant scoping, TenantAware trait, observer behaviour, isScopedToTenant, and tenant switching. Activates when adding tenant-aware models, fixing company_id scoping, working with Filament::getTenant, debugging tenant isolation, or when the user mentions company scope, tenant, multi-tenancy, or company_id.
Configures Filament panel providers. Activates when adding a new panel, registering module resources in a panel, configuring tenant middleware, adjusting auth or theme settings, or when the user mentions PanelProvider, viteTheme, discoverResources, or panel configuration.
Defines the Filament v4 resource page structure used in this project: Resource + Pages + Schemas + Tables split, action patterns, and BaseResource conventions.
Creates and modifies code inside a modular Laravel structure. Targets internachi/modular (modules as real Composer packages with src/). Activates when adding a new module, adding a model/factory/migration/resource/service to an existing module, registering a module with Filament, or when the user mentions modules, modular, or a specific module name.
Works with models that have non-standard primary key names. Activates when writing factories, tests, relationships, or seeders for models that use a custom primary key instead of id.
| name | ci-schema-invariant-gate |
| description | Ensures correct execution order of migrations, seeders, and tests in CI |
Enforces correct execution order of database setup and test execution in CI.
CI MUST run in this order:
php artisan migrate:fresh --seed
php artisan test
No deviations allowed.
This skill ONLY controls:
It does NOT validate:
These are handled by other skills.
If CI fails:
CI does NOT interpret or classify failures.
Test execution MUST always run on a fresh database state created by:
migrate:fresh --seed
No cached or partial state is allowed.
CI defines execution order only.
It does not define correctness of the system.