Codegen Sync Skill
SkillCommunicationVerifies TypeScript codegen is in sync with Elixir protocol definitions. Use this skill after modifying Elixir structs, protocol messages, or RPC types in lib/opal/ to regenerate and verify the TypeScript client SDK types.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Codegen Sync Skill skill
What this skill tells your AI
The instructions your AI receives, as published by matteing/opal in .claude/skills/codegen-sync/SKILL.md and read by ahel’s review.
This project uses code generation to keep TypeScript SDK types in sync with Elixir protocol definitions. When Elixir types change, the TypeScript side must be regenerated.
When to act
- After modifying any Elixir structs, message types, or RPC definitions in
lib/opal/. - After adding or changing tool schemas in
lib/opal/tool/. - When CI fails with a codegen drift error.
- When the user asks to sync or regenerate types.
Commands
# Run codegen (Elixir -> TypeScript)
mix run scripts/codegen_ts.exs
# Verify codegen is up to date (what CI runs)
mix run scripts/codegen_ts.exs --check
Workflow
- After modifying Elixir protocol types, run
mix run scripts/codegen_ts.exs. - Review the generated diff in
cli/src/sdk/to verify correctness. - Include the regenerated files in the same commit as the Elixir changes.
Rules
- Never hand-edit generated files. Always regenerate from the Elixir source.
- If codegen output looks wrong, fix the Elixir definitions or the codegen script (
scripts/codegen_ts.exs), not the output. - Always commit codegen output alongside the source changes — never in a separate commit.
Signals
- GitHub stars
- 59
- Forks
- 2
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
codegen-sync- Source
- github.com/matteing/opal