Claude Code plugin marketplace for Elixir development
# Add to your Claude Code skills
git clone https://github.com/georgeguimaraes/claude-code-elixirGuides for using ide extensions skills like claude-code-elixir.
Last scanned: 5/30/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-05-30T16:02:45.512Z",
"npmAuditRan": true,
"pipAuditRan": true
}claude-code-elixir is an open-source ide extensions skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by georgeguimaraes. Claude Code plugin marketplace for Elixir development. It has 153 GitHub stars.
Yes. claude-code-elixir passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/georgeguimaraes/claude-code-elixir" and add it to your Claude Code skills directory (see the Installation section above).
claude-code-elixir is primarily written in Shell. It is open-source under georgeguimaraes on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other IDE Extensions skills you can browse and compare side by side. Open the IDE Extensions category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh claude-code-elixir against similar tools.
No comments yet. Be the first to share your thoughts!
Top skills in this category by stars
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Claude Code plugins for Elixir development.
claude plugin marketplace add georgeguimaraes/claude-code-elixir
Install all plugins:
claude plugin install elixir-lsp@claude-code-elixir && \
claude plugin install mix-format@claude-code-elixir && \
claude plugin install mix-compile@claude-code-elixir && \
claude plugin install mix-credo@claude-code-elixir && \
claude plugin install elixir@claude-code-elixir
Install the expert binary and make sure it's on your PATH. See installation instructions.
Note:
mix-format,mix-compile, andmix-credorequire bash (Git Bash or WSL on Windows).
| Plugin | Type | Description |
|---|---|---|
| elixir-lsp | LSP | Language Server with completions, go-to-definition, diagnostics |
| mix-format | Hook | Auto-format .ex/.exs files on save |
| mix-compile | Hook | Compile with --warnings-as-errors on save |
| mix-credo | Hook | Run Credo code quality checks on save |
| elixir | Skills | BEAM architecture, Phoenix, Ecto, OTP patterns |
Elixir Language Server integration powered by Expert.
| Feature | Description |
|---|---|
| Navigation | Go to definition, find references |
| Completions | With signature help and docs |
| Diagnostics | Compiler warnings and errors |
| File types | .ex, .exs, .heex, .leex |
Auto-runs mix format after editing .ex and .exs files.
Auto-runs mix compile --warnings-as-errors after editing .ex files.
.ex files (not .exs scripts/tests)mix.exs by walking up directoriesAuto-runs mix credo after editing .ex and .exs files to check code quality.
.ex and .exs filesParadigm-shifting skills for Elixir, Phoenix, and OTP development. Includes a SessionStart hook that auto-suggests skills when working on Elixir code.
Included skills:
| Skill | Use When |
|---|---|
elixir-thinking |
Designing modules, processes, data structures |
phoenix-thinking |
Working with Phoenix, LiveView, PubSub |
ecto-thinking |
Working with Ecto, contexts, schemas |
otp-thinking |
Implementing GenServers, supervisors, Tasks |
Mental models for writing Elixir — how it differs from OOP.
| Concept | Insight |
|---|---|
| Iron Law | NO PROCESS WITHOUT A RUNTIME REASON |
| Three dimensions | Behavior, state, mutability are decoupled |
| Processes | For runtime (state/concurrency/faults), not code organization |
| "Let it crash" | Means "let it heal" — supervisors restart |
| Polymorphism | Behaviors → Protocols → Message passing (least to most dynamic) |
Architectural patterns for Phoenix and LiveView.
| Concept | Insight |
|---|---|
| Where to load data | mount/3 by default; handle_params/3 for live navigation (push_patch) |
| Initial double-load | mount and handle_params both run twice; use connected?/1, assign_async/3, or assign_new/3 |
| Scopes (1.8+) | Security-first authorization threading |
| PubSub | Scoped topics, broadcast_from to avoid self-broadcast |
| Channel fastlane | Socket state can be stale — re-fetch or include in broadcast |
Architectural patterns for Ecto and contexts.
| Concept | Insight |
|---|---|
| Contexts | Bounded domains with their own "dialect" |
| Cross-context refs | Use IDs, not belongs_to associations |
| Schemas | Multiple changesets per schema, embedded_schema for forms |
| Preloads | Separate vs join — pick based on data shape |
| pool_count vs pool_size | pool_count = DBConnection pools, pool_size = connections per pool |
OTP design patterns and when to use each abstraction.
| Concept | Insight |
|---|---|
| Iron Law | GENSERVER IS A BOTTLENECK BY DESIGN |
| ETS | Bypasses bottleneck — concurrent reads with :read_concurrency |
| Task.Supervisor | THE pattern for async work (not raw Task.async) |
| Registry + DynamicSupervisor | Named dynamic processes without atom leaks |
| Broadway vs Oban | External queues vs background jobs — different problems |
elixir-lsp: client/registerCapability workaround. Claude Code's LSP client doesn't respond to client/registerCapability requests that Expert sends during initialization (anthropics/claude-code#32595). The plugin includes a Python wrapper (expert-wrapper) that intercepts these requests and auto-responds so Expert can initialize properly. The wrapper will be removed once the upstream fix lands. Requires Python 3 on PATH.
expert not found: Ensure the expert binary is on your PATH. See installation instructions.
Copyright (c) 2025 George Guimarães
Licensed under the Apache License, Version 2.0. See LICENSE for details.