Skip to content

existential-birds/beagle / plugins/beagle-elixir/skills/elixir-writing-docs

elixir-writing-docs

Verified

Guides writing Elixir documentation with @moduledoc, @doc, @typedoc, doctests, cross-references, and metadata. Use when adding or improving documentation in .ex files.

FileKindSize
SKILL.mdskill md9.0 KB
references/admonitions-and-formatting.mdmarkdown7.1 KB
references/cross-references.mdmarkdown4.3 KB
references/doctests.mdmarkdown6.8 KB

references/doctests.md

View on GitHub
# Doctests

## When to Use Doctests

Doctests serve double duty: they are runnable examples in your documentation **and** lightweight tests. Use them for:

- **Pure functions** with deterministic output
- **String/data transformations** where the input and output are easy to read
- **Simple calculations** and formatting helpers
- **Demonstrating API usage** to new developers

```elixir
@doc """
Converts a price in cents to a formatted dollar string.

## Examples

    iex> MyApp.Format.price_in_dollars(1050)
    "$10.50"

    iex> MyApp.Format.price_in_dollars(0)
    "$0.00"

    iex> MyApp.Format.price_in_dollars(7)
    "$0.07"
"""
def price_in_dollars(cents) when is_integer(cents) and cents >= 0 do
  "$#{div(cents, 100)}.#{cents |> rem(100) |> Integer.to_string() |> String.pad_leading(2, "0")}"
end
```

## When NOT to Use Doctests

Skip doctests when the function:

- **Touches the database** -- results depend on test state
- **Makes HTTP requests** or calls external services
- **Depends on time** -- `DateTime.utc_now/0`, timers, TTLs
- **Produces random output** -- UUIDs, tokens, nonces
- **Has side effects** -- sends emails, writes files, publishes messages
- **Returns large or complex structures** -- hard to read and brittle

```elixir
# BAD - database dependency
@doc """
    iex> MyApp.Accounts.create_user(%{email: "test@example.com"})
    {:ok, %User{}}
"""

# BAD - time dependent
@doc """
    iex> MyApp.Token.generate_expiring()
    %{token: "abc", expires_at: ~U[2025-01-01 12:00:00Z]}
"""

# GOOD - write a regular ExUnit test instead
test "create_user/1 persists a valid user" do
  assert {:ok, %User{email: "test@example.com"}} =
           MyApp.Accounts.create_user(%{email: "test@example.com"})
end
```

## iex> Syntax Basics

### Single-Line Expressions

Each doctest begins with `iex>` followed by a space and the expression. The expected result goes on the next line, unindented relative to `iex>`:

```elixir
@doc """
    iex> String.upcase("hello")
    "HELLO"
"""
```

### Multi-Line Expressions

Use `...>` for continuation lines. The result still follows on the next line:

```elixir
@doc """
    iex> %{name: "Alice", role: :admin}
    ...> |> MyApp.Accounts.display_name()
    "Alice (admin)"
"""
```

### Multiple Examples in One Docstring

Separate independent examples with a blank line:

```elixir
@doc """
    iex> MyApp.Math.clamp(15, 0, 10)
    10

    iex> MyApp.Math.clamp(-3, 0, 10)
    0

    iex> MyApp.Math.clamp(5, 0, 10)
    5
"""
```

### Binding Variables Across Lines

Variables bound in one `iex>` line carry forward within the same example block:

```elixir
@doc """
    iex> list = [3, 1, 4, 1, 5]
    iex> Enum.sort(list)
    [1, 1, 3, 4, 5]
"""
```

## Testing Error Tuples

Return error tuples directly:

```elixir
@doc """
    iex> MyApp.Validation.parse_age("not a number")
    {:error, :invalid_integer}

    iex> MyApp.Validation.parse_age("-5")
    {:error, :must_be_positive}

    iex> MyApp.Validation.parse_age("25")
    {:ok, 25}
"""
```

## Testing Exceptions

Use `** (ExceptionModule)` syntax:

```elixir
@doc """
    iex> MyApp.Validation.parse_age!(nil)
    ** (ArgumentError) expected a string, got: nil
"""
```

The message after the exception module name is matched as a prefix, so you do not need the full message if it is long. However, the exception module must match exactly.

```elixir
# Matches any FunctionClauseError regardless of message
@doc """
    iex> MyApp.Math.factorial(-1)
    ** (FunctionClauseError)
"""
```

## Doctests with Structs

### Inspect-Based Output

When a struct implements the `Inspect` protocol with a custom format, match against that format:

```elixir
@doc """
    iex> MyApp.Money.new(1099, :USD)
    #MyApp.Money<$10.99 USD>
"""
```

### Default Struct Inspect

By default, structs inspect as `%Module{}`:

```elixir
@doc """
    iex> MyApp.Coordinate.origin()
    %MyApp.Coordinate{x: 0, y: 0}
"""
```

### Partial Matching with Pattern Variables

When a struct has fields you cannot predict (like IDs or timestamps), avoid doctests. Write a regular test instead, or only test the fields you control:

```elixir
# Instead of a doctest, use a regular test:
test "build/1 sets the correct defaults" do
  coord = MyApp.Coordinate.build(%{x: 5})
  assert coord.x == 5
  assert coord.y == 0
end
```

## Setting Up Doctests in Test Files

Add `doctest` to any ExUnit test file:

```elixir
defmodule MyApp.FormatTest do
  use ExUnit.Case, async: true

  # Run all doctests in the module
  doctest MyApp.Format

  # Additional unit tests
  test "price_in_dollars/1 handles large values" do
    assert MyApp.Format.price_in_dollars(1_000_000) == "$10000.00"
  end
end
```

You can also place doctests in a dedicated file:

```elixir
defmodule MyApp.DoctestTest do
  use ExUnit.Case, async: true

  doctest MyApp.Format
  doctest MyApp.Math
  doctest MyApp.Validation
end
```

### Running Specific Doctests

```bash
# Run all tests in a file containing doctests
mix test test/my_app/format_test.exs

# Run a specific doctest by line number (line of the iex> prompt in source)
mix test test/my_app/format_test.exs:14
```

## Common Gotchas

### Whitespace Sensitivity

The expected output must match **exactly**, including whitespace. Trailing spaces will cause failures that are hard to spot:

```elixir
# This will FAIL if inspect output has no trailing space
@doc """
    iex> inspect(%{a: 1})
    "%{a: 1} "
"""
```

### Map Key Ordering

Maps with atom keys are printed in alphabetical order by `inspect/1`. Match that order:

```elixir
# GOOD - keys in alphabetical order
@doc """
    iex> MyApp.Config.defaults()
    %{host: "localhost", port: 4000, scheme: :https}
"""

# BAD - keys in insertion order (will fail)
@doc """
    iex> MyApp.Config.defaults()
    %{scheme: :https, host: "localhost", port: 4000}
"""
```

### String Escaping

Strings containing special characters must match the inspected form:

```elixir
@doc """
    iex> MyApp.CSV.escape("value with \\"quotes\\"")
    "\\"value with \\\\\\\"quotes\\\\\\\"\\""
"""
```

When string escaping gets complex, skip the doctest and write a regular test for clarity.

### Large or Multiline Output

If output spans many lines, it becomes brittle. Prefer regular tests:

```elixir
# BAD - long output makes doctest fragile and hard to read
@doc """
    iex> MyApp.Report.generate(:monthly)
    %{
      title: "Monthly Report",
      sections: [
        %{name: "Revenue", ...},
        ...
      ]
    }
"""

# GOOD - test what matters in a regular test
test "generate/1 returns a report with expected sections" do
  report = MyApp.Report.generate(:monthly)
  assert report.title == "Monthly Report"
  assert length(report.sections) == 3
end
```

### Opaque Types

You cannot match on the internals of an `@opaque` type in a doctest. Instead, show usage patterns:

```elixir
@doc """
    iex> conn = MyApp.Connection.open("localhost", 5432)
    iex> is_struct(conn, MyApp.Connection)
    true
"""
```
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 197kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 197kUpdated Claude CodeCodexVerifiedInstall