gateway-dialyzer

Run dialyzer on the Yuzu Erlang gateway to detect type violations.

15|7|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/Tr3kkR/Yuzu --skill gateway-dialyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gateway-dialyzer
Source: https://github.com/Tr3kkR/Yuzu/tree/main/.claude/skills/gateway-dialyzer
Command: npx skills add https://github.com/Tr3kkR/Yuzu --skill gateway-dialyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Runbook ensures static type analysis is applied to the Yuzu Erlang gateway after edits, catching dialyzer warnings and type-clarity issues that the compiler may miss.

Core Features & Use Cases

  • Mandatory post-edit checks: Enforces dialyzer analysis to detect -spec violations, unreachable patterns, dead code, missing transitive dependencies, and opaque type leaks.
  • PLT management guidance: Guides creation and maintenance of the PLT to keep dialyzer fast and accurate across OTP versions and dependencies.
  • Workflow discipline: Advocates running compile, unit tests, and dialyzer checks in a disciplined sequence for safe merges.

Quick Start

From the repo root, run the dialyzer workflow after gateway Erlang edits to catch type issues before commit.

Frequently Asked Questions about gateway-dialyzer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run dialyzer checks on Erlang gateway code after edits?

To run dialyzer checks on Erlang gateway code, execute the dialyzer workflow from the repository root after making edits to detect type violations before committing. This enforces static type analysis to catch issues the compiler misses.

What type of errors does dialyzer catch in an Erlang gateway build?

Dialyzer catches -spec violations, unreachable patterns, dead code, missing transitive dependencies, and opaque type leaks in an Erlang gateway build. It performs static analysis to identify type-clarity issues that the standard compiler may overlook.

How do I maintain the PLT for dialyzer to keep it fast and accurate?

Maintain the PLT for dialyzer by updating it across OTP versions and dependencies to ensure fast and accurate analysis. Proper PLT management guidance involves creating and updating the persistent lookup table to resolve transitive dependencies.

Why does dialyzer fail to resolve transitive dependencies in my Erlang application?

Dialyzer fails to resolve transitive dependencies when required applications are not listed in the configuration. You must ensure all required applications are listed so dialyzer can accurately resolve transitive dependencies during static type analysis.

What is the best workflow sequence for safe merges when checking Erlang type safety?

The best workflow for safe merges involves running compile, unit tests, and dialyzer checks in a disciplined sequence. This ensures type safety and static analysis are applied to the Erlang gateway before any code changes are merged.

When should I run static analysis on my Erlang gateway project?

You should run static analysis on your Erlang gateway project immediately after making gateway Erlang edits. Mandatory post-edit checks ensure dialyzer catches type violations and spec issues early, maintaining code quality before commit.