174 skills (repositories by oliver-kriska) · sorted by popularity
Map 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.
The English summary is being prepared. Showing the original description.
Design 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.
The English summary is being prepared. Showing the original description.
Verify 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.
The English summary is being prepared. Showing the original description.
Start 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.
The English summary is being prepared. Showing the original description.
Analyze 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.
The English summary is being prepared. Showing the original description.
Plan 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.
The English summary is being prepared. Showing the original description.
Triage review findings interactively — approve, skip, or prioritize each issue. Use after /phx-review to filter findings before fixing.
The English summary is being prepared. Showing the original description.
Build and harden Phoenix auth and security — OAuth login, password; Use when adding login flows or permissions…
The English summary is being prepared. Showing the original description.
Run a portable sequential plan-work-verify-review-compound lifecycle. Use optional generic workers only when the runtime supports them.
The English summary is being prepared. Showing the original description.
Execute 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.
The English summary is being prepared. Showing the original description.
Tidewave MCP runtime tools — debugging, smoke testing, live state; Use when evaluating code in a running Phoenix app.
The English summary is being prepared. Showing the original description.
Record a vetted Hex package version in hex_vet.exs after a security review — manages the audit ledger, not the scanner. Use to approve a dep after /phx-deps-audit findings or to initialize hex_vet.exs.
The English summary is being prepared. Showing the original description.
Use when the user asks which /phx-* command fits a task (review, plan, debug, test) or how two commands differ. Checks plans and git state, then recommends from the routing table. Not for bare /help, a tour, or ambiguous requests (intent-detection).
The English summary is being prepared. Showing the original description.
Investigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence, and use optional native DeepSeek Harness subagents only when useful.
The English summary is being prepared. Showing the original description.
Capture solved problems as searchable solution docs. Use after fixing bugs, when "that worked", or after successful /phx-review or /phx-investigate.
The English summary is being prepared. Showing the original description.
Watch an Elixir/Phoenix PR for new review comments (bot + human); Use after opening a PR or pushing, while waiting on…
The English summary is being prepared. Showing the original description.
Execute Elixir/Phoenix plan tasks with progress tracking. Use after $elixir-phoenix:phx-plan to implement features…
The English summary is being prepared. Showing the original description.
Investigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence, and use optional native OpenCode subagents only when useful.
The English summary is being prepared. Showing the original description.
Capture solved problems as searchable solution docs. Use after fixing bugs, when "that worked", or after successful /skill:phx-review or /skill:phx-investigate.
The English summary is being prepared. Showing the original description.
Write or repair Elixir tests with ExUnit, sandbox isolation, async; Use for test files, test setup, or failing/flaky…
The English summary is being prepared. Showing the original description.
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (/phx-investigate).
The English summary is being prepared. Showing the original description.
Watch 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.
The English summary is being prepared. Showing the original description.
Review changed Elixir/Phoenix code read-only. Check requirements, cite evidence, deduplicate, and return a verdict.
The English summary is being prepared. Showing the original description.
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning…
The English summary is being prepared. Showing the original description.