feat(skills-next): add elixir SDK references

[evanpurkhiser]

Direct LLM port of the existing elixir SDK skill into the skills-next per-SDK reference layout under skills-next/references/sdks/elixir/. This content has NOT been reviewed at all — it is a machine-generated port of the existing SDK skill, and every file should be treated as unverified.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 8059788. Configure here.}

[cursor]

Logger handler wrong config app

Medium Severity

The Quick Start nests Sentry.LoggerHandler under config :sentry, logger: [...] but activates handlers with Logger.add_handlers(:my_app). Elixir only loads :logger handlers from the OTP app passed to add_handlers, so the handler block is never applied and crash forwarding stays disabled.

Additional Locations (1)

• skills-next/references/sdks/elixir/logging.md#L22-L39

 

^{Reviewed by Cursor Bugbot for commit 8059788. Configure here.}

[sentry]

Bug: The pattern match on the result of Sentry.capture_check_in is non-exhaustive. It doesn't handle the documented :ignored or {:error, _} return values, which will cause a MatchError.
_{Severity: HIGH}

Suggested Fix

Update the example code to handle all possible return values from Sentry.capture_check_in/1. Use a case statement to pattern match on {:ok, check_in_id}, :ignored, and {:error, _} to prevent MatchError exceptions and handle each case gracefully.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: skills-next/references/sdks/elixir/crons.md#L114

Potential issue: The example code for the `monitor/3` helper function uses a
non-exhaustive pattern match: `{:ok, check_in_id} = Sentry.capture_check_in(...)`. The
`Sentry.capture_check_in/1` function is documented to also return `:ignored` or
`{:error, _}` in common scenarios, such as when a DSN is not configured or the
environment is filtered. If these values are returned, the pattern match will fail and
raise a `MatchError`, crashing the process. Since this is example code intended for
developers to copy, it creates a risk of production crashes in their applications if
they use it directly.