lc:spatie-permissions-audit

Audit Laravel authorization for spatie/laravel-permission inconsistencies.

12|2|Updated Apr 8, 2026

Search Tags:#authorization #security #audit #permissions #laravel #spatie

Ready to run

npx skills add https://github.com/edulazaro/laraclaude --skill lc-spatie-permissions-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lc:spatie-permissions-audit
Source: https://github.com/edulazaro/laraclaude/tree/main/skills/spatie-permissions-audit
Command: npx skills add https://github.com/edulazaro/laraclaude --skill lc-spatie-permissions-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves authorization gaps in Laravel applications using spatie/laravel-permission by identifying undefined permissions, unused roles, and security misconfigurations that lead to silent authorization failures.

Core Features & Use Cases

Comprehensive Audit: Cross-references defined permissions in seeders and migrations against actual usage in Blade, controllers, and middleware.
Security Hardening: Detects unprotected routes and guard mismatches that could leave sensitive endpoints exposed.
Automated Remediation: Offers safe, confirmation-based fixes for missing permissions, incorrect middleware aliases, and stale cache issues.

Quick Start

Run the spatie permissions audit on the entire project to identify and report all authorization issues.

Frequently Asked Questions about lc:spatie-permissions-audit

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

FAQPage Schema

How do I audit spatie/laravel-permission setups for security gaps?▼

Auditing spatie/laravel-permission involves cross-referencing defined permissions in seeders and migrations against actual usage in Blade, controllers, and middleware. This detects undefined permissions, unused roles, and guard mismatches that cause silent authorization failures and expose sensitive endpoints.

Why does my Laravel application have silent authorization failures with spatie permissions?▼

Silent authorization failures occur due to undefined permissions, incorrect middleware aliases, and stale cache issues. These inconsistencies happen when defined permissions in seeders do not match actual usage in controllers, Blade templates, and middleware configurations across the application lifecycle.

What is the best way to find unused roles and dead code in a Laravel authorization system?▼

The best way to find unused roles and dead code is to perform a comprehensive audit that cross-references codebase references, database definitions, and middleware configurations. This detects undefined permissions, unused roles, and security misconfigurations within your Laravel application's authorization setup.

Can I automatically fix guard mismatches and unprotected routes in Laravel?▼

Yes, you can automatically fix guard mismatches and unprotected routes using automated remediation techniques. This approach offers safe, confirmation-based fixes for missing permissions, incorrect middleware aliases, and stale cache issues while validating guard consistency across your application.

How do I ensure proper registration of authorization aliases across my Laravel application lifecycle?▼

To ensure proper registration of authorization aliases, you must validate guard consistency and analyze middleware configurations across the application lifecycle. This verifies that defined permissions are correctly registered and prevents silent authorization failures in your Laravel application.