phx:challenge

Performs adversarial code review of Elixir and Phoenix projects using predefined checklists and lenses.

517|35|Updated Feb 12, 2026

Search Tags:#testing #quality assurance #code review #elixir #phoenix #ecto #liveview

Ready to run

npx skills add https://github.com/oliver-kriska/claude-elixir-phoenix --skill phx-challenge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: phx:challenge
Source: https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/plugins/elixir-phoenix/skills/challenge
Command: npx skills add https://github.com/oliver-kriska/claude-elixir-phoenix --skill phx-challenge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a rigorous, adversarial review process for Elixir and Phoenix code, ensuring higher quality by proactively identifying potential issues before they reach production.

Core Features & Use Cases

Mode-Specific Scrutiny: Offers tailored review checklists for Ecto migrations/queries, LiveView event handling, and general Pull Request readiness.
Adversarial Lenses: Applies universal checks like "What Would Break This?" and "Assumption Stress Test" to all code under review.
Use Case: Before merging a critical Ecto migration that modifies a high-traffic table, use /phx:challenge ecto to ensure it's safe, performant, and backward-compatible.

Quick Start

Initiate a rigorous review of your Ecto changes using the command /phx:challenge ecto.

Frequently Asked Questions about phx:challenge

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

FAQPage Schema

What is adversarial code review for Elixir and Phoenix applications?▼

Adversarial code review for Elixir and Phoenix systematically questions code through predefined checklists to uncover potential bugs, performance bottlenecks, and security vulnerabilities before approval.

How do I review Ecto migrations and queries for high-traffic tables?▼

Review Ecto migrations and queries by applying tailored checklists that verify performance, backward compatibility, and safety, ensuring critical database changes are safe before merging.

Can I use this to check LiveView event handling in my Phoenix application?▼

Yes, you can check LiveView event handling using mode-specific scrutiny tailored for Phoenix applications, ensuring event logic is robust and free of potential issues before approval.

Does rigorous Phoenix code review apply assumption stress tests to pull requests?▼

Yes, rigorous Phoenix code review applies universal adversarial lenses like assumption stress tests and 'what would break this' checks to all code under review to uncover hidden vulnerabilities.

What is the best way to ensure a Phoenix pull request is ready for production?▼

The best way to ensure Phoenix pull request readiness is enforcing adversarial review patterns that proactively identify potential issues, performance bottlenecks, and security vulnerabilities before they reach production.