Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
laravel-audit-conventions
laravel-audit-conventions
mrpunyapal/laravel-auditor
claude-code
conventions
audit
version-aware
anti-patterns
upgrades
dependencies

Audit a Laravel application for framework conventions: anti-patterns, version-appropriate APIs, and misuse of framework features. Use when auditing Laravel conventions.

Install
php artisan boost:add-skill mrpunyapal/laravel-auditor

Save this content to: .claude/skills/laravel-audit-conventions/SKILL.md

# Laravel Conventions Audit

Audit the application for Laravel framework conventions. **The rules must be version-aware whenever the installed version is known.**

List applicable rules first:

```bash
php artisan auditor:rules --domain=conventions --applicable
```

## What to look for

- Framework anti-patterns: patterns that fight the framework's intended flow.
- Unnecessary custom code where standard Laravel mechanisms are clearly better: custom auth loops instead of guards, manual pagination instead of `paginate`, custom file handling instead of storage, etc.
- Version-inappropriate APIs when the version is known: deprecated or removed methods, old-style helpers, `facades` used in ways removed in the installed version.
- Incorrect framework assumptions: `config()` keys that don't exist, middleware that isn't applied, routes that don't match registered patterns.
- Misuse of framework lifecycle/features: service providers doing work in `register()`, observers/mutators causing side effects, cache keys without invalidation, queueable misuse, scheduling misconfig.
- Configuration, validation, routing, jobs, events, policies, resources, commands, notifications, mail, queues, scheduling, and caching used in problematic ways.
- Abandoned runtime dependencies (`AUD-DEP-002`) or license conflicts for a commercial product (`AUD-DEP-003`) — only with `composer show` / license evidence, not because a package is old.

## Evidence requirements

Every conventions finding needs at least:

- The installed Laravel version (from `project_info`).
- The code in question (file + line/range).
- The idiomatic Laravel alternative and why it is better.

## False positives

- Custom code may exist for good reasons the framework mechanism cannot serve — verify before recommending replacement.
- Only recommend replacement when the standard mechanism is clearly better.
- Do not flag style preferences as findings.

## Severity guidance

- `high`: usage that is broken or will break on upgrade.
- `medium`: clear anti-pattern with maintenance cost.
- `low`: minor convention drift.
- `info`: observations.

Laravel Conventions Audit

Audit the application for Laravel framework conventions. The rules must be version-aware whenever the installed version is known.

List applicable rules first:

php artisan auditor:rules --domain=conventions --applicable

What to look for

  • Framework anti-patterns: patterns that fight the framework's intended flow.
  • Unnecessary custom code where standard Laravel mechanisms are clearly better: custom auth loops instead of guards, manual pagination instead of paginate, custom file handling instead of storage, etc.
  • Version-inappropriate APIs when the version is known: deprecated or removed methods, old-style helpers, facades used in ways removed in the installed version.
  • Incorrect framework assumptions: config() keys that don't exist, middleware that isn't applied, routes that don't match registered patterns.
  • Misuse of framework lifecycle/features: service providers doing work in register(), observers/mutators causing side effects, cache keys without invalidation, queueable misuse, scheduling misconfig.
  • Configuration, validation, routing, jobs, events, policies, resources, commands, notifications, mail, queues, scheduling, and caching used in problematic ways.
  • Abandoned runtime dependencies (AUD-DEP-002) or license conflicts for a commercial product (AUD-DEP-003) — only with composer show / license evidence, not because a package is old.

Evidence requirements

Every conventions finding needs at least:

  • The installed Laravel version (from project_info).
  • The code in question (file + line/range).
  • The idiomatic Laravel alternative and why it is better.

False positives

  • Custom code may exist for good reasons the framework mechanism cannot serve — verify before recommending replacement.
  • Only recommend replacement when the standard mechanism is clearly better.
  • Do not flag style preferences as findings.

Severity guidance

  • high: usage that is broken or will break on upgrade.
  • medium: clear anti-pattern with maintenance cost.
  • low: minor convention drift.
  • info: observations.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
shitoudev/permissionmanager
johannesclimacus/laravel-tui
hocvt/seotools
vitalybaev/sypexgeo
amphibee/themosis-ignition
gito-me/fast-excel
frankyso/laravel-ipaymu
geolize-studio/laravel-chile
boomerangui/chat
jinas/dhivatar
store-doc/laravel-storage-driver
plus-it/laravel-translation-manager
diephp/perhaps
diephp/telegraph
osmaviation/spreadsheet
microsoft/fluentui-system-icons
mmccook/php-json-canonicalization-scheme
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console