phx-learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections
Install / Use
npx skills add oliver-kriska/claude-elixir-phoenix --skill phx-learn-from-fixInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Content & MediaSupported Platforms
Our assessment of phx-learn-from-fix
phx-learn-from-fix scores 87/100 on our quality scale, 618th of 1,143 Content & Media skills we index.
Its SKILL.md is 6.8 KB long, well organised into 17 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.
It has 574 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated 13 days ago, so phx-learn-from-fix is actively maintained.
- Our last check on 2026-11-01 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-06. Automated pattern scan on 2026-10-05. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
phx-learn-from-fix compared with similar skills
All 4 of these similar skills score higher than phx-learn-from-fix; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| phx-learn-from-fix (this skill)by oliver-kriska | 87 | 574 | 13d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 113.3k | 12d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 80.2k | today | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 104.4k | 2d ago | MCP Server |
| crawl4aiby unclecode | 100 | 87.6k | today | MCP Server |
Frequently asked questions
- How do I install phx-learn-from-fix?
- Run
npx skills add oliver-kriska/claude-elixir-phoenix --skill phx-learn-from-fix. The install tabs above show the steps for each supported agent. - Which AI agents does phx-learn-from-fix work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is phx-learn-from-fix safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is phx-learn-from-fix still maintained?
- The repository was last updated 13 days ago, so phx-learn-from-fix is actively maintained.
Skill content
View source on GitHubname: phx-learn-from-fix description: Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
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
phx-learn-from-fix --library ical --scope personal ICal.to_ics output needs CRLF line endings
phx-learn-from-fix --library ical --scope project Use method: "PUBLISH" for calendar feeds
Workflow
Step 1: Verify the Lesson
Persist only one of:
- A completed fix verified by tests, reproduction, or user confirmation
- An explicit rule the user taught or asked to save
Stop without writing if neither condition is met.
Do not save a hypothesis, unverified workaround, investigation narrative, or
unsolved error. Use phx-compound for a detailed completed investigation.
Capture the root cause as a concise actionable rule, not the symptom.
Step 2: Select the Route
When both --library <package> and --scope personal|project are present,
use the Library Route. Require both flags; do not guess scope.
For the skill directory only, trim surrounding whitespace and lowercase the
package name. Preserve underscores when forming directory names
(phoenix_live_view becomes hex-phoenix_live_view).
Validate the normalized name against ^[a-z][a-z0-9_]+$. If it does not match,
ask for a valid Hex package identifier instead of replacing characters or
inventing a name. Use the trimmed original identifier, not the normalized
directory name, to look up mix.lock.
Without --library, use the General Correction Route.
Step 3: Check Existing Knowledge
Check if already documented:
- Grep project CLAUDE.md and
~/.claude/CLAUDE.mdfor the pattern keyword - Check auto-memory files for similar lessons
- For library lessons, inspect both
~/.claude/skills/hex-<package>/SKILL.mdand.claude/skills/hex-<package>/SKILL.md - Read
references/common-mistakes.md(read-only plugin reference)
Do not duplicate the same lesson across CLAUDE.md, memory, and a package skill. If the same rule exists, merge wording or report it as already captured.
Library Route
Plugin files are read-only: files under ~/.claude/plugins/ are cached
and get overwritten on updates. Package skills are user-owned files, never
plugin cache files.
Resolve Scope and Precedence
| --scope | Canonical destination |
|-----------|-----------------------|
| personal | ~/.claude/skills/hex-<package>/SKILL.md |
| project | .claude/skills/hex-<package>/SKILL.md |
Personal skills override same-named project skills. If a personal
hex-<package> skill exists, never unknowingly create or update a shadowed
project skill: explain the conflict and ask whether to update personal scope or
keep distinct project-only knowledge. If project scope already exists before a
personal write, warn that the new skill will shadow it and offer to merge or
move it. Maintain one canonical skill per package unless the user explicitly
needs distinct scope-specific rules; never create one skill per lesson.
Read the Locked Version
Inspect mix.lock for the package. Record the exact locked version when found.
If it is absent, say the lesson is not tied to a locally locked version and do
not invent one. Qualify version-sensitive rules. When two verified rules
conflict across versions, preserve both with explicit version ranges instead of
replacing either.
Create or Safely Update the Skill
For a new package skill, create:
---
name: hex-<package>
description: <Package/module/API/task trigger terms for this knowledge>
user-invocable: false
---
# <Package> Knowledge
## Verified Rules
- **<Rule>** (verified with <package> <version>): <actionable guidance>
Make the description precise: include the Hex package, Elixir module names,
important APIs/file formats, and tasks that should trigger this knowledge.
Activation is model-selected from this description; package presence in
mix.lock does not guarantee activation.
Before updating an existing skill, read all of it. Preserve unrelated and hand-authored sections. Merge semantically identical rules. If safe merging is unclear, show the conflict and ask instead of overwriting content.
Do not add paths: to a personal package skill by default: it is a file-path
activation gate, not a dependency predicate. Add paths: only to project scope
when explicitly appropriate and meaningful package-specific paths exist.
General Correction Route
Choose the narrowest non-library destination:
| Scope | Write to | Example |
|-------|----------|---------|
| This project | Project CLAUDE.md | "Never use raw SQL in this app" |
| This project across sessions | Project-keyed auto-memory | "jsonb uses string keys" |
| All your projects | ~/.claude/CLAUDE.md personal instructions | "Prefer explicit error tuples" |
| Detailed completed fix | .claude/solutions/ via phx-compound | Debugging narrative |
For project or personal instructions, preserve existing content and append
**RULE NAME** — Do NOT [bad]. Instead [good] under the relevant category. Use
personal instructions only for rules that should load in every project. For
auto-memory, append to the project-keyed
~/.claude/projects/{project-hash}/memory/MEMORY.md:
### Lesson: [Title]
- **Pattern**: Do NOT [bad] — instead [good]
- **Why**: [root cause explanation]
If the lesson is universal to the plugin rather than one project or package, suggest a plugin contribution; never write it into cached plugin files.
Output
After capturing, confirm:
Lesson captured in [location]
Pattern: Do NOT [bad pattern] — instead [good pattern]
Category: [Ecto/LiveView/OTP/Testing/etc]
Version: [locked package version, not found, or not applicable]
For package skills, also state that description-based activation is
model-selected, not guaranteed by mix.lock.
Iron Laws
- NEVER write generated knowledge to plugin cache — use only the user-owned destinations above
- DO NOT duplicate existing lessons — always check CLAUDE.md and memory before writing
- NEVER overwrite hand-authored content — read both package skill scopes and merge safely
- ONLY persist verified knowledge — completed fixes or explicit user-taught rules, never hypotheses
- DISCLOSE scope precedence — a global package skill shadows its project counterpart
References (READ-ONLY — do NOT edit)
references/common-mistakes.md— Common Elixir mistakes reference. Consult when checking for duplicates.
Related Skills
Agent-Reach
113.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
80.2kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Scrapling
104.4k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
crawl4ai
87.6kOfficial Crawl4AI Cloud: a hosted web scraping, extraction, and search API for AI agents. Free API key, 1,000 credits a month, no card. Fully open source: this repo is the Apache-2.0 crawler that powers it, and you can self-host it.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
