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
review-performance
alizharb/agent-skills
claude-code
performance
n+1-queries
eager-loading
caching
queues
livewire
pagination

Use when reviewing Laravel code for database, queue, cache, API, Livewire, or rendering performance.

Install
php artisan boost:add-skill alizharb/agent-skills

Save this content to: .claude/skills/review-performance/SKILL.md

# Review Performance

## When To Use

Use this skill when code touches growing datasets, loops, queries, rendering, APIs, queues, caches, Livewire, or external calls.

## Inputs Needed

- Expected data size, access pattern, query paths, response needs, queues, caches, and test or profiling output.

## Workflow

1. Identify hot paths and growth risks.
2. Check query count, eager loading, selected columns, pagination, indexes, and aggregate strategy.
3. Check loops for repeated database, cache, network, or filesystem calls.
4. Check queues for slow or retryable work.
5. Check caches for correctness, invalidation, and stampede risks.
6. Check Livewire components for excessive state, missing keys, and unnecessary requests.
7. Recommend focused fixes with measurable value.

## Files That May Be Created

- Performance regression tests where stable and valuable.

## Files That May Be Modified

- Queries, models, migrations, Actions, jobs, caches, resources, Livewire components, and tests if fixing issues is requested.

## Architecture Rules

- Performance fixes should preserve boundaries and avoid moving logic into presentation layers.

## Testing Requirements

- Prefer behavior tests plus targeted query-count or regression tests only when they are stable.

## Security Requirements

- Do not cache private data in shared scopes.
- Avoid leaking data through broad eager loads or resources.

## Review Checklist

- N+1 queries, pagination, indexes, selected columns, aggregates, cache invalidation, queue boundaries, external timeouts, payload size, Livewire request volume, and memory use.

## Common Mistakes

- Caching before fixing query shape.
- Adding brittle query-count tests.
- Doing external calls inside loops or transactions.

Review Performance

When To Use

Use this skill when code touches growing datasets, loops, queries, rendering, APIs, queues, caches, Livewire, or external calls.

Inputs Needed

  • Expected data size, access pattern, query paths, response needs, queues, caches, and test or profiling output.

Workflow

  1. Identify hot paths and growth risks.
  2. Check query count, eager loading, selected columns, pagination, indexes, and aggregate strategy.
  3. Check loops for repeated database, cache, network, or filesystem calls.
  4. Check queues for slow or retryable work.
  5. Check caches for correctness, invalidation, and stampede risks.
  6. Check Livewire components for excessive state, missing keys, and unnecessary requests.
  7. Recommend focused fixes with measurable value.

Files That May Be Created

  • Performance regression tests where stable and valuable.

Files That May Be Modified

  • Queries, models, migrations, Actions, jobs, caches, resources, Livewire components, and tests if fixing issues is requested.

Architecture Rules

  • Performance fixes should preserve boundaries and avoid moving logic into presentation layers.

Testing Requirements

  • Prefer behavior tests plus targeted query-count or regression tests only when they are stable.

Security Requirements

  • Do not cache private data in shared scopes.
  • Avoid leaking data through broad eager loads or resources.

Review Checklist

  • N+1 queries, pagination, indexes, selected columns, aggregates, cache invalidation, queue boundaries, external timeouts, payload size, Livewire request volume, and memory use.

Common Mistakes

  • Caching before fixing query shape.
  • Adding brittle query-count tests.
  • Doing external calls inside loops or transactions.
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