Find Ecto N+1 queries and missing preloads. Use only when N+1 is suspected; not for broad database performance.
Skills in this repository
oliver-kriska/claude-elixir-phoenix - Page 5
SkillsMP has collected 247 skills from oliver-kriska/claude-elixir-phoenix. Open a skill to review its source and details.
oliver-kriska/claude-elixir-phoenixShowing 40 of 247 collected skills.
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task; Use when designing processes or debugging BEAM…
Fetch HexDocs for Elixir libraries with HTML-to-markdown conversion. Use when looking up docs on hexdocs.pm…
Build LiveView: async data (assign_async), PubSub (check connected?); Use when handling interactions, debugging…
Inspect LiveView socket assigns for memory bloat — missing; Use when LiveView memory grows or you need to add…
Narrow bare rescue in Elixir so real errors like KeyError and typos; Use to audit rescues and refactor error handling.
Oban job processing — workers, perform/1 (OSS) and process/1 (Pro); Use when writing Oban workers, queue config…
Phoenix context design — creating/splitting contexts, Scope (1.8+); Use when editing contexts, routers, or designing…
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls…
Brainstorm Elixir/Phoenix features — explore ideas, compare; Use when vague idea, not sure how to approach, or want…
Interactive briefing of a plan file — explains reasoning, schema; Use when developers need to understand a plan…
Challenge mode reviews - rigorous questioning before approving changes. Use when you want thorough scrutiny of Ecto…
Fix Elixir/Phoenix code until Codex CLI review comes back clean; Use when codex is installed and you want an external…
Update Hex dependencies safely. Use for upgrades; use $elixir-phoenix:phx-investigate for deps.get failures.
Recommend the right $elixir-phoenix:phx-* workflow. Use when choosing a plugin skill, not for Codex /help.
Investigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence; Codex subagents are optional.
Reduce mix output noise (5-15% token savings) by installing rtk; Use when long mix output floods context.
Recommend safe Bash permissions for Elixir mix commands in; Use when permission prompts slow workflow, "fix…
Implement small Phoenix changes without planning — add validations; Use for single-file edits under 50 lines.
Recall prior work from past sessions — how a bug was fixed, what was; Use when asked 'have we done this before'…
Review changed Elixir/Phoenix code read-only. Check requirements, cite evidence, deduplicate, and return a verdict.
Analyze Elixir/Phoenix technical debt — duplicates, refactoring; Use when asked about code quality, cleanup, or what…
Triage review findings interactively — approve, skip, or prioritize; Use after $elixir-phoenix:phx-review to filter…
Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs…
Watch an Elixir/Phoenix PR for new review comments (bot + human); Use after opening a PR or pushing, while waiting on…
Investigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence, and use optional native OpenCode subagents only when useful.
Review changed Elixir/Phoenix code read-only. Check requirements, cite evidence, deduplicate findings, and return a severity-based verdict.
Searchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
Inspect LiveView socket assigns for memory bloat — missing temporary_assigns, unused assigns, unbounded lists needing streams, memory estimates. Use when LiveView memory grows or you need to add temporary_assigns.
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
Interactive briefing of a plan file — explains reasoning, schema decisions, component choices. Use when developers need to understand a plan before approving.
Challenge mode reviews - rigorous questioning before approving changes. Use when you want thorough scrutiny of Ecto changes, LiveView events, OTP designs, or PR readiness.
Fix Elixir/Phoenix code until Codex CLI review comes back clean — bounded review, fix, verify loop before opening a PR. Use when codex is installed and you want an external cross-model critic on your changes before pushing.
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (/skill:phx-investigate).
Investigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence, and use optional Pi subagents only when useful.
Reduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.
Recommend safe Bash permissions for Elixir mix commands in settings.json. Use when permission prompts slow workflow, "fix permissions", "reduce prompts", "auto-allow mix".
Implement small Phoenix changes without planning — add validations, update routes, fix components, create migrations. Use for single-file edits under 50 lines.