ecto-n1-check
The ecto:n1-check skill detects N+1 query anti-patterns in Elixir Phoenix applications, specifically identifying Repo calls inside loops and missing association preloads. Use this skill when N+1 query performance issues are explicitly suspected in Ecto code, not for general database optimization or unrelated Ecto questions.
git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix /tmp/ecto-n1-check && cp -r /tmp/ecto-n1-check/targets/amp/skills/ecto-n1-check ~/.claude/skills/ecto-n1-checkSKILL.md
# N+1 Query Detection Identify and fix N+1 query anti-patterns in Ecto/Phoenix applications. ## Iron Laws - Never Violate These 1. **Never access associations without preload** - Always preload before `Enum.map` 2. **No Repo calls inside loops** - Restructure to batch queries 3. **Preload at context boundary** - Load associations in context, not controllers/views 4. **Use joins for filtering** - Use `join` + `preload` when filtering by association ## Detection Patterns ### Pattern 1: Enum.map with Repo ```elixir # BAD: N+1 queries users |> Enum.map(fn user -> Repo.get(Order, user.order_id) end) # GOOD: Single query with preload users |> Repo.preload(:orders) ``` ### Pattern 2: Association Access Without Preload ```elixir # BAD: Lazy loading triggers N queries for user <- users do user.posts # Triggers query for each user! end # GOOD: Eager load first users = Repo.all(User) |> Repo.preload(:posts) for user <- users do user.posts # Already loaded end ``` ### Pattern 3: Nested Association Access ```elixir # BAD: N+1 for nested associations user.posts |> Enum.map(fn post -> post.comments end) # GOOD: Nested preload Repo.preload(user, posts: :comments) ``` ## Quick Detection Commands Use Grep with context lines (`-B 5 -A 5`) to find `Enum.map` near `Repo.` calls in `lib/**/*.ex`. Use Grep to find association access patterns (`.posts`, `.comments`, `.orders`) in `lib/**/*.ex`. Use Grep with context (`-B 3`) to find `Repo.get` or `Repo.one` near loop patterns (`for`, `Enum`) in `lib/**/*.ex`. ## Analysis Command For a context module, run: Use Grep to find all `Repo.` calls in the context module, then verify each has appropriate preloads. Then verify each query has appropriate preloads. ## References For detailed patterns, see: - `references/preload-patterns.md` - Efficient preloading strategies - `references/query-optimization.md` - Query batching techniques
|
|
Analyzes skill effectiveness data to identify failure patterns and recommend improvements. Use after /skill-monitor flags underperforming skills.
Run ad-hoc PostgreSQL analytics queries against dev/test database
Analyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues. Use when asked about code quality, cleanup, or what to improve.
|
|
Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing.