0030-laravel-daily-workflow

Automate Laravel daily startup, migrations, queues, and quality gates.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MrJmpl3/codex_____data_____configuration --skill 0030-laravel-daily-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 0030-laravel-daily-workflow
Source: https://github.com/MrJmpl3/codex_____data_____configuration/tree/main/skills/0030-laravel-daily-workflow
Command: npx skills add https://github.com/MrJmpl3/codex_____data_____configuration --skill 0030-laravel-daily-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents common start-of-day issues in Laravel development by giving a repeatable checklist to bring services up, align database schema, and validate queues and quality gates before you hand off or continue work.

Core Features & Use Cases

  • Start required services: Bring up the local Laravel environment (typically via Laravel Sail) and confirm it is running before continuing.
  • Migrate the schema: Apply database migrations to ensure the current codebase matches the database structure.
  • Ensure background work and tests pass: Start queue workers when needed and run quality gates (Pint) plus parallel test execution; optionally run frontend lint/type checks if the project includes them.

Use case: You switch tasks each morning or before handing off to a teammate and want to avoid stale migrations, failing lint, or broken background jobs.

Quick Start

Run the Laravel daily workflow by executing the full checklist commands to start services, run migrations, run queue workers if needed, and finish with Pint and parallel tests.

Frequently Asked Questions about 0030-laravel-daily-workflow

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

FAQPage Schema
How do I set up a daily Laravel workflow to start services and run migrations?

A daily Laravel workflow starts Sail to bring up local services, runs artisan migrate to align the database schema, and validates queues before development. This repeatable checklist prevents stale migrations and broken background jobs when switching tasks.

What is the best way to validate Laravel queues and tests before handing off code?

Validating Laravel queues and tests before handoff requires starting queue workers with retry limits and running artisan test in parallel. This workflow ensures background jobs function correctly and the test suite passes before a teammate continues your work.

Can I run Laravel Pint and parallel tests together in a pre-handoff checklist?

Yes, you can run Laravel Pint and parallel tests together to enforce quality gates before handoff. The workflow applies Pint formatting checks and executes artisan test in parallel to verify code style and functionality simultaneously.

Does the Laravel daily workflow support frontend lint and type checks with pnpm?

The Laravel daily workflow optionally runs pnpm lint and pnpm type checks if the project includes frontend packages. This ensures both backend Laravel services and frontend dependencies pass quality validation during the start-of-session routine.

Why should I run artisan migrate and Sail up at the start of a Laravel session?

Running artisan migrate and Sail up at the start of a Laravel session prevents common start-of-day issues by ensuring local services are active and the database structure matches the current codebase. This avoids schema misalignment during development.

What limitations should I expect when automating Laravel Sail and queue checks?

When automating Laravel Sail and queue checks, the workflow requires executing Sail up or ps for service validation and conditionally running queue:work with retry limits. It assumes a local environment using Sail, artisan, and optionally pnpm for frontend checks.