Ecto Constraint Debug

What it does

This skill allows an AI agent to debug Ecto constraint issues within Elixir and Phoenix applications. It helps identify the root cause of validation errors, incorrect data types, or other constraint violations that prevent database operations from succeeding. The agent can analyze error messages and suggest fixes based on Ecto's schema definitions.

When to use it

• When encountering cryptic "constraint violation" errors in your Phoenix application’s database interactions.
• During development when rapidly iterating on data models and needing quick feedback on constraint correctness.
• To assist junior developers or those less familiar with Ecto's schema validation process.
• For automated testing of data integrity by simulating invalid inputs and verifying error handling.

Key capabilities

• Error message analysis
• Schema definition interpretation
• Constraint violation identification
• Fix suggestion

Example prompts

• "I'm getting a constraint violation error: 'email cannot be blank'. What does my schema say about the email field?"
• "My Ecto schema for User has a validation that age must be greater than 18. How can I test this constraint?"
• "The database operation failed with an error related to uniqueness constraints. Can you help me understand which fields are involved and why the conflict occurred?"

Tips & gotchas

This skill requires access to your Elixir/Phoenix project's schema definitions (e.g., lib/your_app/repo.ex). Ensure the AI agent has sufficient context about your application’s data models for accurate analysis and suggestions.