Menü
Fetch and convert HexDocs pages for focused library lookups.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Recommend the right `$elixir-phoenix-*` skill for the current task.
Elixir/Phoenix: Review lifecycle, state-machine, Oban, persistence, pause/resume, retry, and restart-sensitive changes before commit, push, or PR. Use for concurrency-sensitive runtime work to produce explicit blocking vs optional findings, require durability checks, and verify smoke plus restart resilience when applicable.
Capture a solved Phoenix problem as a reusable solution doc.
Audit LiveView assigns for memory bloat, dead assigns, and stream candidates.
Audit project health across architecture, security, performance, tests, and deps.
Analyze Phoenix context boundaries and coupling with `mix xref`.
| name | elixir-phoenix-hexdocs-fetcher |
| description | Fetch and convert HexDocs pages for focused library lookups. |
| metadata | {"short-description":"Fetch focused HexDocs content"} |
Efficiently fetch Elixir library documentation from hexdocs.pm using Codex web tools (web.search_query and web.open).
When researching libraries:
# Fetch library overview (known URL)
web.open("https://hexdocs.pm/oban")
# Fetch specific module docs
web.open("https://hexdocs.pm/phoenix_live_view/Phoenix.LiveView.html")
# Discover docs URL first, then open it
web.search_query("Oban.Worker site:hexdocs.pm")
web.open("{selected_result_url}")
Codex web tools extract page content so you can summarize key sections quickly:
| Source | Raw HTML | With Codex web tools | Benefit |
|---|---|---|---|
| HexDocs page | ~80k tokens | ~15k tokens | 80% reduction |
| Phoenix docs | ~120k tokens | ~25k tokens | 79% reduction |
| README | ~20k tokens | ~8k tokens | 60% reduction |
When evaluating libraries, fetch docs efficiently:
web.open("https://hexdocs.pm/oban")
# Library overview
https://hexdocs.pm/{library}
# Module documentation
https://hexdocs.pm/{library}/{Module}.html
https://hexdocs.pm/{library}/{Module.Submodule}.html
# Guides
https://hexdocs.pm/{library}/guides.html
https://hexdocs.pm/{library}/{guide-name}.html
# API reference
https://hexdocs.pm/{library}/api-reference.html
Use focused extraction goals for better summaries:
# For API docs
Extract all public function docs with @spec and examples.
# For guides
Extract the complete guide content preserving code examples.
# For troubleshooting
Extract troubleshooting sections, common errors, and FAQs.
# For configuration
Extract configuration options and their defaults.
Codex may cache repeated fetches internally. Still prefer reusing prior notes within the same plan/research folder.
For longer persistence, save summaries under planning artifacts:
.codex/plans/{slug}/research/docs-oban.md
If Tidewave MCP is available, prefer mcp__tidewave__get_docs for exact version-matched documentation:
mcp__tidewave__get_docs(module: "Oban.Worker")
This fetches docs for the exact version in your mix.lock.