agentsclimarketplace

Laravel migration

Skill event4u-app/agent-config/dist/agent-src/skills/laravel-migration

Use when creating a Laravel migration — table prefixes, column naming, multi-tenant awareness, php artisan make:migration. Other stacks: use stack-native migration tooling.From its SKILL.md

Install
npx -y skills add event4u-app/agent-config --skill laravel-migration

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 19 stars19 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

5.5 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it

laravel-migration

When to use

Use this skill when the user asks to create a database migration, add a column, create a table, or modify the schema.

Procedure: Create a migration

  1. Read conventions — Check ./agents/ and AGENTS.md for table prefixes, column naming, multi-tenant setup.
  2. Generate migration — php artisan make:migration create_xyz_table (or add_column, etc.).
  3. Write schema — Follow naming conventions, add indexes for WHERE/JOIN columns, use decimal for money.
  4. Verify — Run migration (php artisan migrate), then rollback (php artisan migrate:rollback) to confirm reversibility.

All projects

  • Use decimal for money — never float.
  • Add indexes for columns used in WHERE clauses and JOINs.
  • Match existing column naming patterns in the same table or domain.
  • Always include a reversible down() method.

Laravel projects

Multi-database architecture

Some projects use multiple database connections. Check config/database.php for connections.

CheckHow
Available connectionsconfig/database.php → 'connections' array
Migration directoriesdatabase/migrations/ (default), check for additional directories
Custom migrate commandsphp artisan list migrate — look for project-specific commands

Always determine which database the table belongs to before creating a migration.

API database migration

php artisan make:migration create_example_table
return new class extends Migration {
    public function up(): void
    {
        Schema::connection('api_database')->create('example_table', function (Blueprint $table): void {
            $table->id();
            $table->unsignedBigInteger('customer_id');
            $table->string('name');
            $table->boolean('is_active')->default(true);
            $table->timestamps();
            $table->softDeletes();

            $table->foreign('customer_id')
                ->references('id')
                ->on('customers')
                ->onDelete('cascade');

            $table->index('is_active');
        });
    }

    public function down(): void
    {
        Schema::connection('api_database')->dropIfExists('example_table');
    }
};

Customer database migration

php artisan make:migration:customer AddWeatherColumn --table=cl_lv_weather

Customer database tables use the cl_ prefix (e.g. cl_user, cl_lv_weather).

Adding a column (with explicit connection)

return new class extends Migration {
    public function up(): void
    {
        Schema::connection('my_connection')->table('example', function (Blueprint $table): void {
            $table->unsignedInteger('new_column')->after('existing_column');
        });
    }

    public function down(): void
    {
        Schema::connection('my_connection')->table('example', function (Blueprint $table): void {
            $table->dropColumn('new_column');
        });
    }
};

Running migrations

# Default connection
php artisan migrate                           # development
php artisan migrate --env=testing             # testing

# Multi-tenant / custom — check AGENTS.md or module docs for project-specific commands
# Example: php artisan migrate:tenants, php artisan migrate --database=tenant

Composer / legacy projects

  • Check where existing migrations live (e.g. core/migrations/).
  • Use the existing migration format and naming conventions in the project.

Column conventions

  • Foreign keys: {entity}_id (e.g. customer_id, user_id)
  • Booleans: is_ prefix (e.g. is_active, is_default)
  • Dates: descriptive suffix (e.g. upload_date, deleted_at)
  • Always use unsignedBigInteger for foreign keys referencing id() columns
  • Use ->after('column') to place new columns logically

Output format

  1. Migration file with up() and down() methods
  2. Model updates if columns or relationships changed

Gotcha

  • Always check if the table/column already exists before creating the migration — the model doesn't always check.
  • Multi-tenant migrations need special handling — customer tables use different prefixes.
  • Don't modify existing migrations that have been deployed — create a new migration instead.
  • The model forgets ->after('column') for column ordering — MariaDB respects it, and it matters for readability.

Do NOT

  • Do NOT create migrations without specifying the correct connection when multiple databases exist.
  • Do NOT create tables without checking the project's naming conventions (prefixes, casing).
  • Do NOT use raw SQL in migrations when Schema builder works.
  • Do NOT forget to make migrations reversible (down method).
  • Do NOT use float for money — use decimal.
  • Do NOT forget indexes on foreign keys and frequently filtered columns.

Adversarial review

Before finalizing a migration, run the adversarial-review skill. Focus on the "Database migrations" attack questions: Can this destroy data? Is rollback possible?

Auto-trigger keywords

  • database migration
  • create migration
  • table prefix
  • column naming
  • add column
  • create table

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 610,677. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.