flows-jj ABI
SkillDev toolsLets your agent change or verify the flows-jj native/WASM ABI and its reproducibility test campaign.
Available today. Use it from your connected AI after setup.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the flows-jj ABI skill
About this skill
Change or verify the flows-jj native/WASM ABI, committed artifact, or reproducibility campaign.
What this skill tells your AI
The instructions your AI receives, as published by smithersai/smithers in .agents/skills/flows-jj-abi/SKILL.md and read by ahel’s review.
Read the ABI campaign, WASM build script, and CONTRIBUTING.md on the revision under test before editing this crate or its committed WASM artifact.
Use a fresh artifact directory for each campaign. The native and committed real-WASM tiers must consume the same deterministic malformed-request corpus; review the reports and hashes, not merely exit status. A smaller local run and an uninstrumented run are narrower evidence than the scheduled campaign and parser ASAN tier. Neither is an exhaustive ABI proof.
The committed WASM bytes have a pinned Rust toolchain and canonical Linux host contract. node crates/flows-jj/build-wasm.mjs --verify compares without writing; the script refuses unsupported hosts. Build on the canonical host before committing artifact bytes and run the required gate for the files changed. Retain the seed, case/step counts, artifact hashes, host, and tier status with any reproducibility claim.
Signals
- GitHub stars
- 422
- Forks
- 50
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Key
flows-jj-abi- Source
- github.com/smithersai/smithers