Menu
Run Sailfin compiler and test verification safely with the required self-hosting and formatting gates.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run the full Sailfin compiler validation pipeline (make clean-build then make check). Use before declaring a feature shipped, before cutting a release, or when you need to verify self-hosting still works after a structural change.
Systematically diagnose why a Sailfin source file or self-hosting build step fails to compile. Isolates the failure, identifies the pipeline stage, escalates to seed-stabilizer or compiler-architect when the fix is non-trivial, and verifies via test-runner. Use whenever `make compile` fails, a .sfn file won't build, or LLVM rejects generated IR.
Systematically diagnose Sailfin compilation, self-hosting, or LLVM lowering failures without adding build-driver workarounds.
Pick up a ready Sailfin Linear or GitHub issue and drive it through branch, implementation, verification, and PR handoff.
Plan Sailfin work in Linear from Initiatives through Projects to session-sized compiler/runtime issues. Use when Codex needs to audit or create Linear planning structure, prioritize production compiler/runtime health and performance, assign Projects/Cycles/priorities/estimates, groom Triage/Backlog/Ready/Blocked queues, or propose/apply bulk Linear issue updates.
Pin the Sailfin seed compiler to a specific released version. Updates bootstrap.toml [seed].version and the compiler [toolchain] floor, fetches the binary, and optionally runs a smoke compile to verify the new seed builds the compiler. Usage: /pin-seed <version> (e.g. /pin-seed v0.5.10-alpha.12 or /pin-seed 0.5.10-alpha.12).
| name | sailfin-check |
| description | Run Sailfin compiler and test verification safely with the required self-hosting and formatting gates. |
Use this skill whenever a task touches Sailfin compiler sources, runtime code, tests, or docs that describe implementation status.
SAILFIN_MEM_LIMIT overrides); do not add ulimit prefixes or PreToolUse guards for ordinary runs.timeout 60; make targets handle their own timeouts..sfn files under compiler/src/ or runtime/ changed, run the formatter before final verification: sfn fmt --write <files> followed by sfn fmt --check <files> (or build/bin/sfn ... when sfn is not on PATH).compiler/src/*.sfn changed, run make compile before test-only validation so tests do not use a stale compiler binary.git diff --check.sfn check <touched files> (or build/bin/sfn check <path>) to catch parse/type/effect errors quickly.make compile when the change touches compiler self-hosting surface, then run the targeted build/bin/sfn test <path> / -k / --tag commands. Use make check when declaring a shipped feature, cutting a release, or after higher-risk changes.make clean-build before rebuilding.docs/status.md first, then the relevant spec/preview page and roadmap if applicable.docs/proposals/; do not mark SFEPs Implemented before Stage1 readiness and self-hosting are complete.In the final response, list the exact command for every check and mark environment limitations separately from agent errors.