Skill

phx:learn-from-fix

Captures lessons from bug fixes and corrections in Phoenix/Elixir projects — Ecto, LiveView, Oban, iron law mistakes. Documents rules in CLAUDE.md or MEMORY.md to prevent repeats.

code-quality

documentation

npx claudepluginhub oliver-kriska/claude-elixir-phoenix --plugin elixir-phoenix

Tool Access

This skill uses the workspace's default tool permissions.

Preview

After fixing a bug or receiving a correction, capture the lesson

Supporting Assets

references/common-mistakes.md

SKILL.md

Similar Skills

design-system

167.4k

Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.

team-skills-platform

ui-demo

167.4k

Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.

team-skills-platform

kotlin-patterns

167.4k

Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.

team-skills-platform

Stats

Parent Repo Stars180

Parent Repo Forks14

Last CommitApr 1, 2026

Actions

View Source View Plugin View on GitHub View README

Learn From Fix

After fixing a bug or receiving a correction, capture the lesson to prevent future mistakes.

Usage

/phx:learn-from-fix Fixed N+1 query in user listing - was missing preload
/phx:learn-from-fix String vs atom key mismatch in params handling
/phx:learn-from-fix LiveView assign_async needs render_async in tests

Workflow

Step 1: Identify the Pattern

Look at recent conversation context. Ask yourself:

What was the root cause? (not the symptom)
Is this a common mistake others might make?
Can it be prevented with a simple rule?

Step 2: Check Existing Knowledge

Check if already documented:

Grep project CLAUDE.md for the pattern keyword
Check auto-memory files for similar lessons
Read ${CLAUDE_SKILL_DIR}/references/common-mistakes.md (READ-ONLY plugin reference — do NOT edit this file)

If already documented, tell the user and stop.

Step 3: Decide Where to Save

CRITICAL: NEVER edit plugin files. Files under ~/.claude/plugins/ are cached and get overwritten on updates. Always write to project or memory locations.

Scope	Write to	Example
This project only	Project CLAUDE.md	"Never use raw SQL in this app"
All Elixir projects	Auto-memory MEMORY.md	"jsonb always uses string keys"
Detailed fix with context	`.claude/solutions/` via `/phx:compound`	Complex debugging story

Step 4: Write the Lesson

For project CLAUDE.md — append a concise rule:

### [Category] Iron Laws (continued)

N. **[SHORT RULE NAME]** — Do NOT [bad pattern]. Instead [good pattern]

For auto-memory — append to ~/.claude/projects/{project-hash}/memory/MEMORY.md:

### Lesson: [Title]
- **Pattern**: Do NOT [bad] — instead [good]
- **Why**: [root cause explanation]

Step 5: Consider Broader Updates

If the lesson is significant enough to be an Iron Law:

Suggest adding to project CLAUDE.md Iron Laws section
If it's universal (applies to all Elixir projects), suggest updating the plugin itself (the user can PR it)

Output

After capturing, confirm:

Lesson captured in [location]

Pattern: Do NOT [bad pattern] — instead [good pattern]
Category: [Ecto/LiveView/OTP/Testing/etc]

Iron Laws

NEVER edit plugin files — files under ~/.claude/plugins/ are cached and overwritten on updates
DO NOT duplicate existing lessons — always check CLAUDE.md and memory before writing
Capture the root cause, not the symptom — "missing preload" not "query was slow"

References (READ-ONLY — do NOT edit)

${CLAUDE_SKILL_DIR}/references/common-mistakes.md — Common Elixir mistakes reference. Consult when checking for duplicates. Ships with the plugin — NEVER modify.