dual-target-check

Validate Gleam formatting and run Erlang and JavaScript target tests.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tylerbutler/birch --skill dual-target-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dual-target-check
Source: https://github.com/tylerbutler/birch/tree/main/.claude/skills/dual-target-check
Command: npx skills add https://github.com/tylerbutler/birch --skill dual-target-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill validates and speeds up cross-target development by ensuring Gleam code is properly formatted and that tests run successfully on both Erlang and JavaScript targets.

Core Features & Use Cases

  • Format checks: Verifies all Gleam source files are properly formatted.
  • Cross-target testing: Executes tests for both Erlang and JavaScript targets to ensure compatibility.
  • Pre-commit/CI readiness: Helps catch issues before commits or PRs in a cross-platform codebase.

Quick Start

Run the quick check to format Gleam sources and execute tests for both targets.

Frequently Asked Questions about dual-target-check

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

FAQPage Schema
How do I run cross-target tests for Gleam on both Erlang and JavaScript?

Cross-target tests for Gleam validate code compatibility by executing standard test suites on both Erlang and JavaScript targets. This skill automates running these tests to ensure code works across both platforms.

What is the best way to check Gleam formatting before a commit?

Checking Gleam formatting before a commit involves verifying that all source files adhere to standard formatting rules. This skill applies pre-commit validation to automatically detect and report any unformatted Gleam code.

Can I use Gleam's standard tooling for CI pipeline cross-target validation?

Yes, Gleam's standard tooling supports CI pipeline cross-target validation. This skill integrates into CI pipelines to sequentially check formatting and run tests for both Erlang and JavaScript targets.

Does cross-target testing for Gleam catch JavaScript and Erlang compatibility issues?

Cross-target testing for Gleam catches compatibility issues by running the same test suite against both the Erlang and JavaScript targets. It ensures platform-specific failures are identified during local development or CI.

Why do I need to run tests on both Erlang and JavaScript targets in Gleam?

Running tests on both Erlang and JavaScript targets in Gleam is necessary because code can compile successfully on one target but fail on another. Cross-target testing ensures true platform compatibility for cross-platform codebases.

When should I not rely on automated Gleam formatting checks?

Automated Gleam formatting checks are unnecessary if your project does not use cross-target compilation or if you manually enforce strict formatting standards locally. This skill targets cross-target changes requiring automated validation.