← ClaudeAtlas

query-analysislisted

Audit Laravel Eloquent and query-builder usage in a user-selected repository without changing application code. Trace HTTP and background paths and write an evidence-backed query analysis report under docs/analysis/.
sebastiansulinski/claude-plugins · ★ 0 · Code & Development · score 62
Install: claude install-skill sebastiansulinski/claude-plugins
# Query analysis Perform a read-only diagnostic pass. The sole filesystem deliverable is one analysis report; creating its parent directory is allowed. Do not fix code or turn this audit into an implementation task. ## Target and boundaries Use the repository path explicitly supplied with the invocation. Resolve relative paths from the invocation's working directory. If no target was supplied, ask for it and wait; do not assume the current repository. Confirm the directory exists and is Laravel, otherwise stop and explain. Read its applicable AGENTS.md, architecture policies, relevant source and tests. Report unavailable source, dependencies or runtime evidence. The default report location is docs/analysis/ under the invocation's working directory, matching the original command's ./docs/analysis/ convention. Honor a user-specified report location. Do not create any other files, run tests, install dependencies, run migrations or invoke application commands other than the optional `php artisan route:list` to map entry points. Prefer reading routes when that is sufficient. No data writes. ## Trace the complete query path Map HTTP entry points and background execution: routes, middleware, observers, listeners, notifications, scheduled commands and queued jobs. Follow calls into actions, services, repositories, datasets, custom Eloquent builders and models. Read complete methods rather than isolated search hits. Include: - Eloquent terminal calls, scopes, aggregates, pagina