Trellis Session Insight
mindfold-ai/Trellis
Reach into past AI conversation history through the trellis mem CLI.
Debug Ecto constraint violations - trace triggers, check migrations, find duplicate data.
Install Ecto Constraint Debug
$ npx skills add oliver-kriska/claude-elixir-phoenix --skill ecto-constraint-debug -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install oliver-kriska/claude-elixir-phoenix ecto-constraint-debug --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .claude/skills && cp -r skills-src/targets/pi/skills/ecto-constraint-debug .claude/skills/ecto-constraint-debug && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ecto-constraint-debug" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/targets/pi/skills/ecto-constraint-debug into .claude/skills/ecto-constraint-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecto-constraint-debug", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/targets/pi/skills/ecto-constraint-debugType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add oliver-kriska/claude-elixir-phoenix --skill ecto-constraint-debug -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install oliver-kriska/claude-elixir-phoenix ecto-constraint-debug --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .agents/skills && cp -r skills-src/targets/pi/skills/ecto-constraint-debug .agents/skills/ecto-constraint-debug && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ecto-constraint-debug" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/targets/pi/skills/ecto-constraint-debug into .agents/skills/ecto-constraint-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecto-constraint-debug", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add oliver-kriska/claude-elixir-phoenix --skill ecto-constraint-debug -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install oliver-kriska/claude-elixir-phoenix ecto-constraint-debug --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/targets/pi/skills/ecto-constraint-debug .cursor/skills/ecto-constraint-debug && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ecto-constraint-debug" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/targets/pi/skills/ecto-constraint-debug into .cursor/skills/ecto-constraint-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecto-constraint-debug", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/oliver-kriska/claude-elixir-phoenix.git --path targets/pi/skills/ecto-constraint-debug--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add oliver-kriska/claude-elixir-phoenix --skill ecto-constraint-debug -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install oliver-kriska/claude-elixir-phoenix ecto-constraint-debug --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/targets/pi/skills/ecto-constraint-debug .gemini/skills/ecto-constraint-debug && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ecto-constraint-debug" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/targets/pi/skills/ecto-constraint-debug into .gemini/skills/ecto-constraint-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecto-constraint-debug", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install oliver-kriska/claude-elixir-phoenix ecto-constraint-debugInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add oliver-kriska/claude-elixir-phoenix --skill ecto-constraint-debug -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .github/skills && cp -r skills-src/targets/pi/skills/ecto-constraint-debug .github/skills/ecto-constraint-debug && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ecto-constraint-debug" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/targets/pi/skills/ecto-constraint-debug into .github/skills/ecto-constraint-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecto-constraint-debug", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add oliver-kriska/claude-elixir-phoenix --skill ecto-constraint-debug -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install oliver-kriska/claude-elixir-phoenix ecto-constraint-debug --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/targets/pi/skills/ecto-constraint-debug .opencode/skills/ecto-constraint-debug && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ecto-constraint-debug" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/targets/pi/skills/ecto-constraint-debug into .opencode/skills/ecto-constraint-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecto-constraint-debug", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ecto-constraint-debug- GitHub stars
- 565
- Token cost
- ~799 tokens
- SKILL.md length
- 352 words
- Files
- 2 (incl. references)
- Skills in repo
- 105
- Repo updated
- First seen
- Licence
- MIT
At a glance
Debug Ecto constraint violations - trace triggers, check migrations, find duplicate data.
- Works in 6 steps: Parse the Error → Find the Migration → Find the Schema → …
- Seeing uniqueconstraint
- SKILL.md covers Iron Laws, Step-by-Step Debugging, Quick Fixes by Constraint Type and References
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ecto Constraint Debug is an agent skill from oliver-kriska/claude-elixir-phoenix. Debug Ecto constraint violations - trace triggers, check migrations, find duplicate data. Use when seeing uniqueconstraint, foreignkeyconstraint, or checkconstraint errors.
Its SKILL.md is about 800 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/constraint-patterns.md`).
It sits in Development, covering Debugging. The repository describes itself as: Claude Code plugin for Elixir/Phoenix/LiveView — 26 specialist agents, Iron Laws enforcement, and Tidewave MCP integration. Plan features with parallel research agents, execute… The licence is MIT.
When your agent uses it
- Seeing uniqueconstraint
- Foreignkeyconstraint
- Checkconstraint errors
Example prompts
- “/ecto-constraint-debug”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 9767a82. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ecto Constraint Debug loads about 799 tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 50 tokens; SKILL.md has 352 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from oliver-kriska/claude-elixir-phoenix at commit 9767a82, republished under its MIT licence (© oliver-kriska). 352 words, ~799 tokens.
Download SKILL.mdSave it as
.claude/skills/ecto-constraint-debug/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- ecto-constraint-debug
- description
- Debug Ecto constraint violations - trace triggers, check migrations, find duplicate data. Use when seeing unique_constraint, foreign_key_constraint, or check_constraint errors.
Ecto Constraint Debugging
Ash projects: Ash surfaces DB constraints through its own error DSL. Use the
ash-frameworkskill —mix usage_rules.search_docs "constraint" -p ash_postgres.
Systematic approach to diagnosing constraint violations. Load when you see Ecto.ConstraintError, unique_constraint, foreign_key_constraint, or constraint-related changeset errors.
Iron Laws
- READ THE CONSTRAINT NAME — The constraint name (e.g.,
links_url_index) tells you exactly which index/constraint failed. Parse it from the error message first - CHECK MIGRATION BEFORE CODE — Verify the constraint definition in
priv/repo/migrations/matches what the schema expects - TRACE ALL INSERT PATHS — Find every code path that inserts into the constrained table. The bug is often in a path you didn't consider
- RACE CONDITION UNTIL PROVEN OTHERWISE — If validation passes but constraint fails, assume concurrent inserts until you prove a single-request cause
Step-by-Step Debugging
Step 1: Parse the Error
Extract from the error message:
- Constraint name (e.g.,
users_email_index) - Table name (e.g.,
users) - Operation (insert, update, or delete)
- Conflicting values (if available in logs)
Step 2: Find the Migration
Use Grep to search for the constraint name in priv/repo/migrations/. Also check for create unique_index, create index, add constraint.
Verify: Does the migration constraint match the schema's unique_constraint/3 or foreign_key_constraint/3 call?
Step 3: Find the Schema
Use Grep to find constraint handling in changesets (unique_constraint, foreign_key_constraint, check_constraint) in lib/.
Show full SKILL.md (140 more words)Show less
Step 4: Trace Insert Paths
Find ALL callers that insert/update this schema:
Use Grep to find all insert/update paths (Repo.insert, Repo.update, Repo.insert_all, cast_assoc) in lib/.
Step 5: Identify the Cause
| Symptom | Likely Cause | Fix Pattern |
|---|---|---|
| Same user triggers twice | Race condition (double-click, retry) | Upsert with on_conflict |
| Multiple parents share child | cast_assoc doesn't dedup across changesets | Dedup before building changesets |
| Concurrent API requests | Missing transaction isolation | Wrap in Repo.transaction or use upsert |
| Migration added constraint to existing data | Data violates new constraint | Backfill or clean data first |
Step 6: Apply Fix
See references/constraint-patterns.md for detailed fix patterns.
Quick Fixes by Constraint Type
Unique violation → Upsert: Repo.insert(changeset, on_conflict: :replace_all, conflict_target: [:field])
Foreign key violation → Check: Does the referenced record exist? Was it deleted concurrently?
Check constraint → Validate: Does the value satisfy the constraint condition?
References
references/constraint-patterns.md- Detailed patterns for each constraint type
© oliver-kriska, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in targets/pi/skills/ecto-constraint-debug of oliver-kriska/claude-elixir-phoenix.
- SKILL.md
- references/constraint-patterns.md
Open the folder on GitHubat commit 9767a82
Compare with similar skills
Ecto Constraint Debug next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ecto Constraint Debug this skilloliver-kriska/claude-elixir-phoenix | 565 | — | ~799 | Automated safety check: Pass | MIT | |
| Trellis Session Insightmindfold-ai/Trellis | 15k | 4 repos | ~1.7k | Automated safety check: Pass | AGPL-3.0 | |
| Native Data FetchingCherryHQ/cherry-studio-app | 4k | 6 repos | ~2.9k | Automated safety check: Notes | MIT | |
| Debugging Executionsn8n-io/n8n | 207k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Aoti Debugpytorch/pytorch | 104k | 1 repos | ~1.7k | Automated safety check: Pass | Custom licence | |
| Herdr Throwaway Reproductionherdrdev/herdr | 43k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Native Data Fetching
CherryHQ/cherry-studio-app
A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.
- Official
Debugging Executions
n8n-io/n8n
Debug failed or wrong-output workflow executions using executions tools.
Aoti Debug
pytorch/pytorch
Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.
Herdr Throwaway Reproduction
herdrdev/herdr
Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.
Systematic Debugging
ultralisp/ultralisp
A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes
More from oliver-kriska/claude-elixir-phoenix
All 105 skills in this repoPhx Brief
oliver-kriska/claude-elixir-phoenix
Interactive briefing of a plan file — explains reasoning, schema decisions, component choices.
Codex Ab
oliver-kriska/claude-elixir-phoenix
Run an A/B codex review experiment — holistic codex review vs 3 focused dimension passes (security, ecto, liveview) on the branch diff, classify findings, report a panel-value verdict.
Audit
oliver-kriska/claude-elixir-phoenix
Project health audit and health check — architecture, performance, tests, dependencies, code quality.
Compound Docs
oliver-kriska/claude-elixir-phoenix
Searchable Elixir/Phoenix/Ecto solution documentation system with; Use when consulting past solutions…
Compound Docs
oliver-kriska/claude-elixir-phoenix
Searchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter.
Deploy
oliver-kriska/claude-elixir-phoenix
Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays.
Related
Categories
Questions about Ecto Constraint Debug
What does Ecto Constraint Debug do?
Debug Ecto constraint violations - trace triggers, check migrations, find duplicate data. Ecto Constraint Debug is an agent skill from oliver-kriska/claude-elixir-phoenix. Debug Ecto constraint violations - trace triggers, check migrations, find duplicate data.
When should I use Ecto Constraint Debug?
Ecto Constraint Debug fits situations like: seeing uniqueconstraint; foreignkeyconstraint; checkconstraint errors.
How do I install Ecto Constraint Debug in Claude Code?
Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill ecto-constraint-debug -a claude-code`. Or copy the skill folder (targets/pi/skills/ecto-constraint-debug in oliver-kriska/claude-elixir-phoenix) into .claude/skills/ecto-constraint-debug in your project. Claude Code loads it when a task matches its description.
How do I install Ecto Constraint Debug in Codex?
Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill ecto-constraint-debug -a codex`. Or copy the skill folder (targets/pi/skills/ecto-constraint-debug in oliver-kriska/claude-elixir-phoenix) into .agents/skills/ecto-constraint-debug in your project. Codex loads it when a task matches its description.
Can I use Ecto Constraint Debug in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add oliver-kriska/claude-elixir-phoenix --skill ecto-constraint-debug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ecto-constraint-debug, .gemini/skills/ecto-constraint-debug, .github/skills/ecto-constraint-debug and .opencode/skills/ecto-constraint-debug in your project.
What does Ecto Constraint Debug need to run?
SKILL.md names no scripts, command-line tools or credentials: Ecto Constraint Debug is instructions for the agent only.
Does Ecto Constraint Debug access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ecto Constraint Debug safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Ecto Constraint Debug use?
Ecto Constraint Debug is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ecto Constraint Debug use?
About 799 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.
What are the alternatives to Ecto Constraint Debug?
Skills that share tags, products or a category with Ecto Constraint Debug: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Debugging Executions (n8n-io/n8n, 207k stars) and Aoti Debug (pytorch/pytorch, 104k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ecto Constraint Debug?
oliver-kriska (a GitHub user) maintains it in oliver-kriska/claude-elixir-phoenix, which has 565 GitHub stars. The repository holds 105 skills in this directory. The repository was last updated on October 5, 2026.
Source: oliver-kriska/claude-elixir-phoenix on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.