Repair Elixir moduledoc, function docs, and specs for target files.
npx skills add https://github.com/wadvanced/aurora_uix --skill documentation-wadvanced
Please help me install this Agent Skill. Skill: documentation Source: https://github.com/wadvanced/aurora_uix/tree/main/.claude/skills/documentation Command: npx skills add https://github.com/wadvanced/aurora_uix --skill documentation-wadvanced
This Skill helps prevent broken or incomplete Elixir documentation by guiding you to add missing moduledocs and function docs, along with required specs, without changing any logic.
@moduledoc, @doc, @spec, and @shortdoc where required.mix consistency to find docs/doctor issues and then fixes only those tied to the provided target file.Run the documentation skill on the single Elixir module file path you want to document so it can address the mix consistency documentation warnings for that file.
High-intent search queries and answers about installing and using this skill.
To fix Elixir moduledoc and typespec warnings reported by mix consistency, you can add or repair missing `@moduledoc`, `@doc`, `@spec`, and `@shortdoc` attributes in your target file without altering any existing code logic.
The best way to add missing function docs and specs to an Elixir module is to iterate on `mix consistency` outputs and apply strict documentation-stage edits, ensuring you add `@doc` and `@spec` attributes while preserving the original logic.
Mix consistency detects documentation and doctor warnings in Elixir by running iterative checks against your codebase, flagging specific `*.ex` or `*.exs` files that lack required `@moduledoc`, `@doc`, or `@spec` attributes.
Yes, you can repair Elixir documentation warnings without changing code logic by applying strict non-invasive rules that only modify documentation attributes and never alter function definitions, ordering, or unrelated internal structures.
No, fixing typespec and moduledoc warnings does not require modifying unrelated code in Elixir. The process enforces strict non-invasive rules, ensuring only doc-stage edits are tied to the specific target file.
wadvancedRun mix consistency and apply stage-specific fixes to Elixir codebases.
mkreymanRun Mix-based quality checks for Elixir/Phoenix projects.
DecoyLexDraft and review Elixir documentation against project style guides and ExDoc conventions.
layeddieStandardize Elixir codebases with official naming, structure, and documentation standards.