elixir-knowledge-patch

Provide updated Elixir, Phoenix, and LiveView API knowledge patches for migrations.

22|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Nevaberry/nevaberry-plugins --skill elixir-knowledge-patch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: elixir-knowledge-patch
Source: https://github.com/Nevaberry/nevaberry-plugins/tree/main/plugins/elixir-knowledge-patch/skills/elixir-knowledge-patch
Command: npx skills add https://github.com/Nevaberry/nevaberry-plugins --skill elixir-knowledge-patch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides concise, curated updates for language and framework changes so developers avoid introducing outdated APIs, deprecated patterns, and breaking behaviors when writing or updating Elixir, Phoenix, and LiveView code.

Core Features & Use Cases

  • Breaking-change summaries: Clear notes on behaviors that now raise, deprecated patterns, and required code adjustments for Elixir 1.19–1.20 and Phoenix 1.8.
  • API and tooling guidance: Lists of new stdlib APIs, mix and compilation changes, and updated project configuration practices.
  • LiveView & frontend patterns: Updated JS hook patterns, colocated hooks, portals, keyed comprehensions, and testing migrations to LazyHTML.
  • Use Case: Run a patch check before generating or refactoring code to ensure generated code uses the correct APIs, avoids deprecated constructs, and follows new compilation and LiveView conventions.

Quick Start

Ask the elixir-knowledge-patch to review your project and produce a prioritized list of code changes required to migrate to Elixir 1.20 and Phoenix 1.8 compatibility.

Frequently Asked Questions about elixir-knowledge-patch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate my Phoenix application to Elixir 1.20 and Phoenix 1.8?

To migrate your Phoenix application to Elixir 1.20 and Phoenix 1.8, review your project against curated breaking-change summaries and updated compilation guidance. You then apply required code adjustments to resolve deprecated patterns and ensure runtime compatibility.

What are the breaking changes in LiveView 1.0 and 1.1?

Breaking changes in LiveView 1.0 and 1.1 include updated JS hook patterns, colocated hooks, and portals. You must adjust your templates and testing migrations to LazyHTML to resolve compilation and runtime breaking changes.

How do I fix deprecated Elixir stdlib APIs during an upgrade?

To fix deprecated Elixir stdlib APIs during an upgrade, check new API summaries and mix compilation guidance. Apply vetted knowledge patches to replace outdated constructs with correct new stdlib APIs in your codebase.

Do I need to update mix configuration for Elixir 1.19 compatibility?

You need to update mix configuration for Elixir 1.19 compatibility to follow new project configuration practices. The patch provides tooling guidance to align your mix and compilation settings with current framework requirements.

What is the best way to avoid outdated Phoenix LiveView patterns when refactoring?

The best way to avoid outdated Phoenix LiveView patterns when refactoring is to run a knowledge patch check first. This ensures your generated code uses correct APIs, avoids deprecated constructs, and follows updated LiveView JS conventions.