debug-cross-platform — community debug-cross-platform, community, ide skills

v1.0.0
GitHub

About this Skill

Perfect for Multi-Language Agents needing systematic cross-platform debugging capabilities across Erlang and JavaScript Debug issues that only occur on one target (Erlang or JavaScript). Use when tests pass on one target but fail on the other.

tylerbutler tylerbutler
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
36
Canonical Locale
en
Detected Body Locale
en

Perfect for Multi-Language Agents needing systematic cross-platform debugging capabilities across Erlang and JavaScript Debug issues that only occur on one target (Erlang or JavaScript). Use when tests pass on one target but fail on the other.

Core Value

Empowers agents to diagnose and resolve FFI implementation mismatches using comprehensive logging and comparison tools like diff, targeting Erlang and JavaScript environments with libraries such as birch_ffi.erl and birch_ffi.mjs

Ideal Agent Persona

Perfect for Multi-Language Agents needing systematic cross-platform debugging capabilities across Erlang and JavaScript

↓ Capabilities Granted for debug-cross-platform

Debugging cross-platform issues in Erlang and JavaScript applications
Identifying FFI implementation mismatches between targets
Comparing debugging logs across different platforms using tools like just test-erlang and just test-js

! Prerequisites & Limits

  • Requires Erlang and JavaScript environments
  • Limited to debugging Erlang and JavaScript applications
  • Needs access to source code files like src/birch_ffi.erl and src/birch_ffi.mjs for comparison

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is debug-cross-platform?

Perfect for Multi-Language Agents needing systematic cross-platform debugging capabilities across Erlang and JavaScript Debug issues that only occur on one target (Erlang or JavaScript). Use when tests pass on one target but fail on the other.

How do I install debug-cross-platform?

Run the command: npx killer-skills add tylerbutler/birch/debug-cross-platform. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for debug-cross-platform?

Key use cases include: Debugging cross-platform issues in Erlang and JavaScript applications, Identifying FFI implementation mismatches between targets, Comparing debugging logs across different platforms using tools like just test-erlang and just test-js.

Which IDEs are compatible with debug-cross-platform?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for debug-cross-platform?

Requires Erlang and JavaScript environments. Limited to debugging Erlang and JavaScript applications. Needs access to source code files like src/birch_ffi.erl and src/birch_ffi.mjs for comparison.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add tylerbutler/birch/debug-cross-platform. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use debug-cross-platform immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

debug-cross-platform

Install debug-cross-platform, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Cross-Platform Debugging

Systematic approach to debugging issues that only occur on Erlang OR JavaScript.

Quick Diagnosis

bash
1# Run on both targets to identify which fails
2just test-erlang
3just test-js

Common Causes

1. FFI Implementation Mismatch

Symptom: Different behavior between targets for the same function.

Check:

bash
1# Compare FFI implementations
2diff <(grep -A 20 "function_name" src/birch_ffi.erl) \
3     <(grep -A 20 "function_name" src/birch_ffi.mjs)

Common issues:

  • Return type mismatch (tuples vs arrays)
  • Error handling differences
  • String encoding (UTF-8 handling)

2. Platform-Specific APIs

Symptom: Function works on one platform, undefined/error on other.

JavaScript-only APIs:

  • process.stdout, process.stderr (Node.js)
  • Deno.isatty() (Deno)
  • console.log behavior varies by runtime

Erlang-only APIs:

  • Process dictionary (erlang:put/get)
  • OTP behaviors (gen_server, etc.)
  • :logger integration

3. Async Behavior

Symptom: Race conditions or timing issues on JavaScript.

Check:

  • Erlang is synchronous by default
  • JavaScript may need await or callbacks
  • Look for Promise handling in FFI

4. Type Coercion

Symptom: Unexpected values or type errors.

Gleam TypeErlangJavaScript
IntIntegerNumber
FloatFloatNumber
StringBinaryString
ListListArray
TupleTupleArray
Nilnil atomundefined

5. TTY/Terminal Detection

Symptom: Color output works on one platform.

Check:

gleam
1// In platform.gleam
2is_stdout_tty()  // Different implementation per platform

Debugging Steps

Step 1: Isolate the Failure

bash
1# Run specific test
2gleam test --target erlang -- --filter "test_name"
3gleam test --target javascript -- --filter "test_name"

Step 2: Add Debug Output

gleam
1// Temporary debug logging
2import gleam/io
3io.debug(value)  // Works on both targets

Step 3: Check FFI

  1. Read src/birch/internal/platform.gleam for declarations
  2. Compare src/birch_ffi.erl and src/birch_ffi.mjs
  3. Look for behavioral differences

Step 4: Test JavaScript Runtimes

bash
1# Test on all JS runtimes
2just test-integration-node
3just test-integration-deno
4just test-integration-bun

Step 5: Check Runtime Detection

In birch_ffi.mjs, verify runtime detection:

javascript
1// Node.js
2typeof process !== 'undefined' && process.versions?.node
3
4// Deno
5typeof Deno !== 'undefined'
6
7// Bun
8typeof Bun !== 'undefined'
9
10// Browser
11typeof window !== 'undefined'

FFI Debugging Checklist

  • Both implementations exist for the function
  • Return types match Gleam declaration
  • Error cases handled identically
  • Edge cases (empty string, null, special chars) tested
  • All JS runtimes have fallbacks (Node, Deno, Bun, browser)

Quick Fixes

IssueErlang FixJavaScript Fix
Undefined functionCheck module exportsCheck export statement
Wrong return typeMatch Gleam type exactlyReturn correct JS type
Encoding issuesUse unicode:characters_to_binaryUse TextEncoder
TTY detectionCheck os:type()Check process.stdout.isTTY

Related Skills

Looking for an alternative to debug-cross-platform or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer