Explore skills
Showing 12601–12630 of 21781 skills
Triage review findings interactively — approve, skip, or prioritize each issue. Use after /phx:review to filter findings before fixing.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexVerify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexWatch an Elixir/Phoenix PR for new review comments (bot + human) and CI results via a background watcher that wakes Claude only on real events. Use after opening a PR or pushing, while waiting on CI or reviewers.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexExecute Elixir/Phoenix plan tasks with progress tracking. Use after /phx:plan to implement features with mix compile and mix test verification after each step, or --continue to resume interrupted work.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexAnalyze a legacy app in any language before rewriting it in Elixir: inventory, features as goals, why each mechanism exists, runtime topology, external contracts. Use to start or refresh a rewrite.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexDesign the idiomatic Elixir architecture for a rewrite: set the compatibility bar (ADR-000), consult phx specialists on open questions, then build contexts, ledger and ADRs. Use after /rewrite:analyze.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexMap mechanisms from any language or framework (Rails, Django, PHP, Node, Go, JVM, .NET, others) to idiomatic Elixir. Use when a rewrite or port needs verdicts, targets, guarantee checks or a translationese review.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexPlan a rewrite as vertical slices and hand each one to /phx:plan as a requirements seed with binding decisions, contracts and acceptance criteria. Use after /rewrite:architect, or for the next slice.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexStart or resume an Elixir rewrite of an app in any language (Rails, Django, PHP, Node, Go, Java, .NET, others) and show its status. Use when someone wants to port, migrate or rewrite an app into Elixir/Phoenix.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexVerify a rewrite slice against its obligations: preflight, capture fresh test evidence, audit translationese and parity, update the ledger. Use after /phx:work finishes a rewrite slice, or before claiming parity.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexWatch an Elixir/Phoenix PR with an Amp Orb keep-alive lease until required non-deployment CI is green and review threads are resolved. Use after opening or updating a PR.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexAsh Framework — resources, actions, policies, aggregates, calculations, AshPhoenix.Form, LiveView, migrations. Use when generating resources via mix ash.codegen, editing changes, checks, types, validations, or domain code interfaces.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexSearchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexElixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexDetect N+1 query anti-patterns specifically — Repo calls inside Enum/for loops, missing preloads on associations. Use when N+1 is explicitly suspected, NOT for unrelated Ecto questions or wider database performance.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexUse when a task touches Ecto, even a how-to question: schemas, changesets, validations, queries, preloads, Multi, migrations, constraints, money fields. Load it before writing Ecto code. Skip for Ash.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexOTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexFetch HexDocs for Elixir libraries with HTML-to-markdown conversion. Use when looking up docs on hexdocs.pm — modules, functions, guides, changelogs.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexRoute ambiguous or mixed Phoenix/LiveView/Ecto requests before choosing a workflow. Use when user is unsure where to start/how to approach work, asks for the right workflow, or combines intents such as fixing and refactoring. NOT for a clear task.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexBuild LiveView: async data (assign_async), PubSub (check connected?), phx-change events, form components/modals/uploads, streams for lists, live_patch. Use when handling interactions, debugging events, or tracking Presence.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexInspect LiveView socket assigns for memory bloat — missing temporary_assigns, unused assigns, unbounded lists needing streams, memory estimates. Use when LiveView memory grows or you need to add temporary_assigns.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexNarrow bare rescue in Elixir so real errors like KeyError and typos propagate instead of being swallowed. Use to audit rescues and refactor error handling.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexUse when writing, scheduling, testing or debugging Oban jobs, even for a how-to question: workers, cron, retries, unique jobs, queues, Pro Workflow/Batch. Load it before touching job code; it holds the job rules.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexPhoenix context design — creating/splitting contexts, Scope (1.8+), Ecto.Multi, PubSub, routers, plugs, controllers. Use when editing contexts, routers, or designing boundaries.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexProject health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexAnalyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexBrainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexInteractive briefing of a plan file — explains reasoning, schema decisions, component choices. Use when developers need to understand a plan before approving.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexChallenge mode reviews - rigorous questioning before approving changes. Use when you want thorough scrutiny of Ecto changes, LiveView events, OTP designs, or PR readiness.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexFix Elixir/Phoenix code until Codex CLI review comes back clean — bounded review, fix, verify loop before opening a PR. Use when codex is installed and you want an external cross-model critic on your changes before pushing.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodex