queues-audit

Analyze Laravel queue and job patterns for idempotency, retry, and concurrency issues.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/jonaaix/laravel-livewire-base --skill queues-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: queues-audit
Source: https://github.com/jonaaix/laravel-livewire-base/tree/main/.ai/skills/queues-audit
Command: npx skills add https://github.com/jonaaix/laravel-livewire-base --skill queues-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps identify and report queue and job pattern issues in a Laravel project.

Core Features & Use Cases

  • Scans Laravel queue usage across controllers, jobs, listeners, events, and configuration to surface idempotency gaps, retry gaps, and concurrency risks.
  • Generates a structured findings report with actionable suggestions, focusing on queueable classes, failure handling, and correct use of Laravel's queue features. Only issues verifiable from repository files are reported.

Quick Start

Run the queues-audit against a Laravel project to produce a structured report of findings.

Frequently Asked Questions about queues-audit

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

FAQPage Schema
How do I audit Laravel queues for job and listener issues?

You identify queue pattern issues by analyzing PHP source files, queue configuration, and tests to surface idempotency, retry, and concurrency concerns across jobs and listeners. This generates a structured report with actionable suggestions.

What queue problems does a Laravel jobs and listeners audit detect?

A Laravel queue audit detects idempotency gaps, retry configuration issues, and concurrency risks within queueable classes. It evaluates failure handling and correct usage of Laravel features to report only issues verifiable from repository files.

How do I check if my Laravel queueable classes have idempotency and concurrency risks?

Check Laravel queueable classes by scanning controllers, jobs, events, and batches for idempotency and concurrency risks. This analysis reviews failure handling and produces a structured report of findings with actionable suggestions.

Does the Laravel queue audit scan vendor and node_modules directories?

No, the Laravel queue audit excludes vendor, node_modules, and storage directories from analysis. It scans your Laravel project's controllers, listeners, jobs, events, configuration, tests, and deployment artifacts to produce findings.

Can I audit Laravel batches and events for queue best practices?

Yes, you can audit Laravel batches and events for best practices by analyzing queueable classes and configuration. The audit surfaces retry gaps and concurrency concerns, generating a structured report of actionable findings.