rewrite

Plugin rewrite from marketplace oliver-kriska in oliver-kriska/claude-elixir-phoenix. Commands read from the repo's manifest — 10 days ago.

Skills (6)

• analyze

  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.

• architect

  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.

• elixir-way

  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.

• roadmap

  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.

• start

  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.

• verify

  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.

Subagents (7)

• contract-surveyor

  Surveys a legacy app's external contracts (DB schema, cookies, crypto, URLs, APIs, webhooks, sockets, files, env) as testable assertions for an Elixir rewrite. Use when /rewrite:analyze needs contracts.md for ADR-000.

• elixir-way-architect

  Synthesizes rewrite analysis and the ADR-000 compatibility bar into an idiomatic Elixir architecture, a complete mechanism ledger, ADRs and divergences. Use when /rewrite:architect has analysis and an accepted bar.

• feature-cartographer

  Maps a legacy app's user-visible capabilities, actors, invariants and acceptance probes before an Elixir rewrite. Use when /rewrite:analyze needs features as goals instead of a file list.

• idiom-auditor

  Audits ported Elixir code for translationese and drift from the rewrite architecture (hand-rolled queues, GenServer-owned DB, mirrored legacy trees, lost guarantees). Use when /rewrite:verify checks a slice.

• infra-topologist

  Maps a legacy app's runtime topology (processes, Redis by role, queues, cron, caches, storage, search, deploy, operator duties) and what each becomes on the BEAM. Use when /rewrite:analyze needs runtime.md.

• mechanism-archaeologist

  Digs up why each legacy mechanism exists (callbacks, jobs, caches, locks, globals) from code, comments and git history, and drafts the rewrite ledger. Use when /rewrite:analyze needs purposes and verdicts.

• parity-auditor

  Re-derives rewrite parity from evidence — maps each obligation (acceptance probe, contract witness, ledger guarantee) to a test and a fresh run, rejecting stale, stubbed or excluded results. Use when /rewrite:verify scores a slice.

Similar plugins