Topic: claude-code-skills
8,614 skills in this topic.
-
ralph-specum-cancel
This skill should be used only when the user explicitly asks to use `$ralph-specum-cancel`, or explicitly asks Ralph Specum in Codex to stop execution or remove a spec.
tzachbon/smart-ralph 278
-
ralph-specum-index
This skill should be used only when the user explicitly asks to use `$ralph-specum-index`, or explicitly asks Ralph Specum in Codex to generate or refresh index artifacts.
tzachbon/smart-ralph 278
-
tdd
Use for every coding task. Enforce strict TDD workflow: activate Serena, investigate first, clarify+confirm requirements, write per-task REQUIREMENTS.md in .requirements/<datetime>_<feature_name>/, verify APIs via web search, then implement in tiny test-verified steps.
Shelpuk-AI-Technology-Consulting/agent-skill-tdd 23
-
skill-monitor
Analyze skill effectiveness across sessions. Computes per-skill metrics (action rate, friction, outcomes), identifies degrading skills, and generates improvement recommendations. Requires session-scan data in metrics.jsonl.
oliver-kriska/claude-elixir-phoenix 252
-
session-scan
Compute metrics for Claude Code sessions. Discovers via ccrider, filters trivial, computes friction/opportunity/fingerprint scores. Use for broad session triage.
oliver-kriska/claude-elixir-phoenix 252
-
phx:challenge
Challenge mode reviews - rigorous questioning before approving changes. Use when you want thorough scrutiny of Ecto changes, LiveView events, or PR readiness.
oliver-kriska/claude-elixir-phoenix 252
-
phx:examples
Provide examples and walkthroughs for Phoenix, LiveView, Ecto, OTP patterns. Use when "how do I...", "show me an example", or "what does X look like".
oliver-kriska/claude-elixir-phoenix 252
-
testing
Elixir testing patterns — ExUnit, Mox, factories, LiveView test helpers. Use when working on *_test.exs, test/support/, factory files, or fixing test failures.
oliver-kriska/claude-elixir-phoenix 252
-
phx:pr-review
Address PR review comments on Elixir/Phoenix code — fetch comments, draft responses, optionally fix code. Use when the user shares a PR URL or mentions reviewer feedback.
oliver-kriska/claude-elixir-phoenix 252
-
phx:trace
Trace Elixir call trees from entry points via mix xref. Use when debugging data flow, planning signature changes, or understanding how a bug reaches code.
oliver-kriska/claude-elixir-phoenix 252
-
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
oliver-kriska/claude-elixir-phoenix 252
-
phx:learn-from-fix
Capture lessons after fixing a bug or receiving a correction — ecto, liveview, oban, iron law mistakes. Use when the user corrects your approach or teaches a pattern.
oliver-kriska/claude-elixir-phoenix 252
-
session-trends
Analyze trends across session metrics. Computes windowed aggregates, deltas, and compares against MEMORY.md findings. Use periodically for progress tracking.
oliver-kriska/claude-elixir-phoenix 252
-
phx:compound
Capture solved problems as searchable solution docs. Use after fixing bugs, when "that worked", or after successful /phx:review or /phx:investigate.
oliver-kriska/claude-elixir-phoenix 252
-
phx:triage
Triage review findings interactively — approve, skip, or prioritize each issue. Use after /phx:review to filter findings before fixing.
oliver-kriska/claude-elixir-phoenix 252
-
phoenix-contexts
Phoenix 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 252
-
phx:full
Use for large features spanning multiple contexts, new domain modules, or when the user wants autonomous end-to-end implementation. Runs the full plan-implement-review-compound cycle with specialist agents and Iron Laws enforcement.
oliver-kriska/claude-elixir-phoenix 252
-
phx:brief
Interactive 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 252
-
ecto-patterns
Ecto patterns — schemas, changesets, queries, migrations, Multi, associations, preloads, upserts. Use when editing Repo calls, Ecto.Query, or schema fields. Skip for Ash.
oliver-kriska/claude-elixir-phoenix 252
-
phx:investigate
Investigate bugs and errors in Elixir/Phoenix — root-cause analysis for crashes, exceptions, stack traces, test failures. Use --parallel for deep 4-track investigation.
oliver-kriska/claude-elixir-phoenix 252
-
elixir-idioms
OTP/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 252
-
phx:plan
Plan multi-step Phoenix features with specialist agents. Use when building new domains, multi-file features, or creating plans from review findings. Use --existing to enhance a plan.
oliver-kriska/claude-elixir-phoenix 252
-
lab:autoresearch
Self-improving loop for plugin skills. Reads program.md, proposes one mutation per iteration, evaluates against deterministic scorer, keeps improvements via git, reverts failures. Targets weakest skill+dimension. Use with /loop for overnight runs.
oliver-kriska/claude-elixir-phoenix 252
-
cc-changelog
CONTRIBUTOR TOOL - Track CC changelog, extract new versions since last check,
analyze impact on plugin (breaking changes, opportunities, deprecations).
Run periodically or before releases. NOT part of the distributed plugin.
oliver-kriska/claude-elixir-phoenix 252