all publishers

facebookexperimental

@facebookexperimental source repo

30 published skills

  1. ▌
    Testing Tools · facebookexperimental
    How to build, run, and test Reverie tools — the nightly toolchain, validate.sh gate, package-scoped cargo commands, the host-dependent test skip list, running the reverie-examples tools (noop/strace/counter/chaos) over a backend, and the reverie-dbt test scripts. Read before validating a Reverie change or writing a new tool.
    207 repo stars
  2. ▌
    Adding A Backend · facebookexperimental
    How to add a new Reverie execution backend — implementing Backend::run<T>, providing a Guest<T> view (regs, memory, inject/tail_inject), wiring GlobalState over reverie-rpc-transport for out-of-process backends, and enumerating serviced syscalls. Read when building or extending a backend (ptrace/KVM/DBT/e9patch).
    207 repo stars
  3. ▌
    Repo Cleanliness · facebookexperimental
    Keep hermit/ and reverie/ clean, focused implementation repos — no experiments, no ai_docs slop, no binaries, no vendored/nested git repos. Use before every commit and whenever staging files or deciding where an artifact belongs.
    207 repo stars
  4. ▌
    Liteinst Testing · facebookexperimental
    Use when adding LiteInst regressions, selecting focused test coverage, diagnosing guest hangs, or reporting backend and determinism evidence.
    207 repo stars
  5. ▌
    Reverie Architecture · facebookexperimental
    Map of the Reverie process-instrumentation framework — the Tool/GlobalTool/Guest/Backend contracts, the crate layout, and how a tool observes and rewrites a guest's syscalls across the ptrace, KVM, and DBT backends. Read this first when working anywhere in reverie.
    207 repo stars
  6. ▌
    Syscall Interception · facebookexperimental
    How a Reverie tool observes and rewrites guest syscalls — declaring subscriptions, the handle_syscall_event hook, inject vs. tail_inject, typed syscalls via reverie-syscalls, reading/writing guest memory, and the per-backend trap mechanisms (ptrace seccomp, DBT, KVM hypercalls). Read when writing or debugging syscall handlers.
    207 repo stars
  7. ▌
    Liteinst Tool Lifecycle · facebookexperimental
    Use when changing LiteInst backend launch, preload bootstrap, tool installation, coordinator RPC, syscall dispatch, injection, signals, or lifecycle callbacks.
    207 repo stars
  8. ▌
    Liteinst Binary Instrumentation · facebookexperimental
    Use when changing LiteInst syscall discovery, text patching, trampolines, executable-map tracking, trap fallback, or allocator scopes.
    207 repo stars
  9. ▌
    Fabler · facebookexperimental
    Apply a disciplined read, plan, execute, and adversarially verify workflow. Use for complex research, architecture, implementation, or audit tasks.
    207 repo stars
  10. ▌
    Progress Rubric · facebookexperimental
    Create evidence-based Hermit progress reports from live measurements. Use when gathering, validating, or writing a project progress report.
    207 repo stars
  11. ▌
    Hermit Debugging · facebookexperimental
    Debug hermit/detcore runs (nondeterminism, hangs, syscall gaps, scheduling) using hermit's built-in logging and log-diff FIRST, before reading source. Use whenever a guest program behaves unexpectedly, --verify fails, or a run hangs under hermit.
    207 repo stars
  12. ▌
    Post Facto Review · facebookexperimental
    Land reviewed, CI-green Hermit changes before human review and mark them for follow-up. Use as the default autonomous landing discipline.
    207 repo stars
  13. ▌
    Human Review First · facebookexperimental
    Gate key Hermit changes on adversarial review and explicit human approval. Use only when the user explicitly requests human-review-first mode.
    207 repo stars
  14. ▌
    Autows Docs · facebookexperimental
    Consult and maintain AutoWS documentation. Use BEFORE exploring AutoWS source code — when investigating, planning, or modifying files under WarpSpecialization/, partition scheduling, warp_specialize ops, WSCodePartition, WSDataPartition, WSTaskPartition, WSMemoryPlanner, or related passes. Also use AFTER making non-trivial changes to AutoWS code to keep docs in sync.
    207 repo stars
  15. ▌
    Ir Debugging · facebookexperimental
    Debug Triton compilation by dumping IR at each stage (TTIR, TTGIR, LLVM, PTX). Use when investigating compilation failures, kernel performance, register spills, or when user asks to inspect IR output. Covers TRITON_KERNEL_DUMP, MLIR_ENABLE_DUMP, LLVM_IR_ENABLE_DUMP, TRITON_DUMP_PTXAS_LOG, and related env vars.
    207 repo stars
  16. ▌
    Autows Testing · facebookexperimental
    Run autoWS (automatic warp specialization) correctness tests. Use when working on autoWS compiler code — files under WarpSpecialization/, partition scheduling, warp_specialize ops, WSCodePartition, WSDataPartition, WSTaskPartition, WSMemoryPlanner, or related passes. Do NOT use TLX correctness tests (third_party/tlx/tutorials/testing/test_correctness.py) for autoWS work — those test manual warp specialization via TLX, not the automatic compiler pipeline.
    207 repo stars
  17. ▌
    Tlx Amd Testing · facebookexperimental
    Test and run TLX-AMD tutorial kernels (gfx950/CDNA4 and gfx1250) and understand their CI. Use when working on AMD TLX tutorial kernels — GEMM (warp-pipeline, LDS-pipelined, TDM, MXFP), Flash Attention (simple, prefetch, persistent), addmm+GLU, or IKBO (FA, LCE) — running their correctness or perf, checking arch gating (gfx950 vs gfx1250), or the MI350 CI workflow. Covers the standardized layout (one correctness file, one perf file per op×arch).
    207 repo stars
  18. ▌
    Autows Authoring · facebookexperimental
    Author Triton kernels with automatic warp specialization (AutoWS). Use when writing new AutoWS kernels, adding warp_specialize=True to tl.range loops, choosing tl.range kwargs and JIT options, debugging why WS was not applied, or structuring a kernel to work with both Meta WS and upstream OAI Triton. Covers GEMM and Flash Attention patterns on Hopper and Blackwell.
    207 repo stars
  19. ▌
    Compute Sanitizer · facebookexperimental
    Run NVIDIA compute-sanitizer (memcheck, racecheck, initcheck, synccheck) against a Triton/TLX kernel to find runtime memory and synchronization bugs. Use when a kernel produces wrong results, crashes with an illegal/misaligned access, or is suspected of a shared-memory data race or invalid barrier usage — especially warp-specialized (WS) kernels using mbarriers, named barriers, TMA copies, or MMA accumulators. This is a runtime check: it runs the real kernel via its reproduce command, so it needs a working GPU and is 10-100x slower than a normal run.
    207 repo stars
  20. ▌
    Debug Failing Gpu · facebookexperimental
    Recover from GPU-busy / GPU-unavailable failures. Use when a command (pytest, python, a TLX/Triton kernel run, a benchmark) fails with errors indicating the GPU is busy, out of memory, or unavailable — e.g. "CUDA error: out of memory", "all CUDA-capable devices are busy or unavailable", "CUDA-capable device(s) is/are busy or unavailable", "RuntimeError: No CUDA GPUs are available", "device-side assert", or a hang on the first CUDA call. Runs find_working_gpu.sh to locate a healthy GPU and re-runs the failed command pinned to it via CUDA_VISIBLE_DEVICES.
    207 repo stars
  21. ▌
    Running With Buck · facebookexperimental
    How to build and run GPU targets under Buck in fbcode. Use when invoking buck2 run / buck2 build for any GPU benchmark, test, or kernel — selecting the GPU architecture and CUDA version, using @mode/opt and the beta Triton modifier, passing environment variables through, and running from the right directory. Covers the general requirements plus the B200/GB200 (b200a, CUDA >= 12.8) and GB300 (b300a, CUDA >= 13.0) hardware requirements.
    207 repo stars
  22. ▌
    Tlx API Reference · facebookexperimental
    TLX DSL API reference for low-level GPU primitives. Use when writing or modifying TLX kernel code that uses barriers (mbarrier, named barriers), memory allocation (local_alloc, SMEM, TMEM), TMA operations, warp specialization (async_tasks, async_task), CLC (cluster launch control), or wgmma instructions. Covers Hopper and Blackwell hardware differences.
    207 repo stars
  23. ▌
    Kernel Perf Testing · facebookexperimental
    Run TLX kernel performance benchmarks on Hopper, Blackwell, and AMD (gfx950/CDNA4, gfx1250) GPUs. Use when user asks to benchmark, profile, or measure performance of any TLX kernel (GEMM, Flash Attention, addmm+GLU, IKBO variants). Handles GPU selection, denoise wrapping (NVIDIA only), and version flags. Never run unless explicitly asked.
    207 repo stars
  24. ▌
    Ir Override Ablation · facebookexperimental bundle
    Design and run Triton TTGIR debugging ablations using ir_override. Use when reducing a provided or dumped TTGIR, trying user-provided or agent-generated ablation/oblation ideas, updating a test harness around ir_override, or preserving a compile/runtime failure while simplifying IR to expose a fundamental compiler or lowering gap.
    207 repo stars
  25. ▌
    Barrier Visualization · facebookexperimental bundle
    Produce a structured barrier report for AutoWS (automatic warp specialization) IR. Use when the user wants to visualize, audit, or debug barrier usage across warp-specialized partitions, or when debugging a GPU kernel hang (deadlock). For hangs, first dump IR using the ir-debugging skill, then run this barrier analysis to find the barrier that actually deadlocks -- reasoning with the mbarrier phase model (NOT raw arrive/wait counts, which give false positives), plus missing backward barriers and other synchronization issues. Covers mbarriers, named barriers, tcgen05 commit, TMA-implicit arrives, Aref-based synchronization, and producer/consumer barrier patterns.
    207 repo stars
  26. ▌
    Proxy Fence Insertion · facebookexperimental
    Use when working on fence-related compiler passes, TMA store lowering, proxy fence insertion, investigating missing or spurious fences, or debugging correctness issues in TLX kernels that use tlx.async_descriptor_store or MMA operations.
    207 repo stars
  27. ▌
    Sched2tlx Perf Testing · facebookexperimental
    Run the sched2tlx perf/correctness harness over the modulo-scheduling example corpus (case1-9: GEMM, persistent GEMM, FA fwd/bwd, addmm+bias, LayerNorm, wgrad+bias, multiphase GEMM, scaled_mm). Use when the user asks to benchmark generated-vs-handwritten kernels, check corpus correctness, compare emitter revisions, or regenerate schedule_graph.json fixtures. Never run perf unless explicitly asked.
    207 repo stars
  28. ▌
    Tma Illegal Instruction · facebookexperimental
    Diagnose CUDA "illegal instruction" / kernel crashes on Triton kernels that reference to TMA loads or stores (`make_tensor_descriptor`, `TensorDescriptor`, `descriptor.load`, `descriptor.store`, `tl.async_descriptor_load`, async TMA copies) as the source code line. Use when the user reports CUDA error 716, "an illegal instruction was encountered", segfault inside a TMA op, kernel hang followed by an illegal instruction trap, or a crash that only fires on the first or last tile of a launch. Covers the pattern where a TMA store/load is issued at an offset entirely past a tensor's shape — TMA does NOT silently mask out-of-bounds tile accesses; it traps. The root cause is almost never "missing in-kernel mask" — it is commonly a structural launcher / tile-mapping bug.
    207 repo stars
  29. ▌
    Amd Att Trace · facebookexperimental bundle
    Collect, validate, package, and inspect rocprofv3 Advanced Thread Trace bundles for AMD GPU kernels. Use for ATT collection, viewer-ready artifacts, or loop cycle windows; do not trigger for ordinary performance benchmarks.
    207 repo stars
  30. ▌
    Tlx Kernel Optimization Agent · facebookexperimental bundle
    Execute the TLX Kernel Optimization Agent CLI on a Triton or TLX kernel. Use this skill whenever the user says "use the TLX agent", "use the kernel optimization agent", "用 TLX agent 优化", or asks Carl/Claude to optimize a kernel with the repository agent. The required outcome is an actual agent CLI invocation and its measured result, not a walkthrough or reimplementation.
    207 repo stars