ketchup
Ketchup is an easter-egg alias for the catchup skill that generates return-from-absence briefings in an Elixir Phoenix project. Use it identically to catchup with all flags passing through unchanged, making it functionally equivalent except for an optional cosmetic footer indicator showing the ketchup emoji.
git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix /tmp/ketchup && cp -r /tmp/ketchup/plugins/catchup/skills/ketchup ~/.claude/skills/ketchupSKILL.md
# Ketchup 🍅 — alias for /catchup
You found the easter egg. `/ketchup` is a 1:1 alias for `/catchup` —
condiment-grade catch-up, no behavior change.
## Iron Laws
1. **Behave identically to `/catchup`** — this file adds nothing; it
only forwards. Never diverge from the canonical skill.
2. **Pass `$ARGUMENTS` through verbatim** — same flags, same defaults.
## Execution
1. Read `${CLAUDE_PLUGIN_ROOT}/skills/catchup/SKILL.md`.
2. Execute that workflow exactly, with this invocation's `$ARGUMENTS`
passed through unchanged (`--since`, `--sources`, `--depth`,
`--focus` all behave the same).
3. In the brief's footer line, you may render the generator as
`/ketchup 🍅` instead of `/catchup` — the only cosmetic difference.
That's it. One condiment, same nutrition.Ash Framework — resources, actions, policies, aggregates, calculations,
Compatibility alias for the Elixir/Phoenix plugin's LiveView assigns audit. Invoke explicitly with /lv:assigns.
Inspect 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.
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
Interactive briefing of a plan file — explains reasoning, schema decisions, component choices. Use when developers need to understand a plan before approving.
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.