Conventions for writing justfile recipes in Nix-based projects.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Every recipe must have a doc comment (# line above the recipe name).
Use a nix_shell variable to auto-detect whether we're inside nix develop:
nix_shell := if env('IN_NIX_SHELL', '') != '' { '' } else { 'nix develop -c' }
Prefix commands that need devshell tools (node, trunk, cargo-watch, etc.) with {{nix_shell}}. Recipes that invoke nix directly (build, run, flake commands) don't need it.
Long chained commands should use multiline \ continuations.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Modern, interactive alternative to `/do` — clarify intent up front, then take a task end-to-end with a serial AI review gauntlet (lens debate (lowy ⇄ hickey) → codex debate → simplify → code-police, each editing the branch in turn) → CI → evidence. ONLY invoke when the user explicitly types `/be` or `$be`; never auto-select from a natural-language request.
日本語の概要は準備中です。原文の説明を表示しています。
Run /be's review gauntlet SERIALLY — /lens-debate (lowy ⇄ hickey), then /codex-debate, then /simplify, then code-police, each editing and committing on the live branch in turn. Use from /be §4, or when the user asks to "run the review gauntlet". Requires Claude Code's Skill tool.
日本語の概要は準備中です。原文の説明を表示しています。
Reference for the `odu` runner — how to invoke a full pipeline, a single recipe, or a platform-pinned node, and how to attach to a live run, from a project whose CI odu runs. Trigger when the user asks to "run CI", "run the pipeline", "re-run a check", to run named lanes or recipes (e.g. "run fmt and nix", "just the e2e lane", bare selectors like `fmt`/`nix`/`e2e`), or names a recipe by `<recipe>@<platform>`. This skill — not a repo's local `just ci` / `just <recipe>` — is how an odu-run request is served.
日本語の概要は準備中です。原文の説明を表示しています。
Review code for quality, simplicity, and common mistakes before declaring work complete.
日本語の概要は準備中です。原文の説明を表示しています。
Run an automated codex⇄Claude debate to consensus — no round cap, no deadlock exit. Two explicit subcommands. `review` (also the bare/back-compat default) — codex (reviewer) critiques the current diff and a Claude subagent (author) fixes/disputes, looping until they agree. `answer` — Claude and codex each answer a freeform prompt in parallel, then cross-check until they agree, and a unified answer is returned. Use when the user types `/codex-debate`, asks to "have codex review this", "run the codex debate", "review this PR with codex", "argue this with codex until you agree", or passes a question to "have Claude and codex debate/answer until they agree".
日本語の概要は準備中です。原文の説明を表示しています。
Do a task end-to-end — implement, PR, CI loop, ship. ONLY invoke when the user explicitly types `/do` or `$do`; never auto-select from a natural-language request, even one that sounds like an end-to-end task.
日本語の概要は準備中です。原文の説明を表示しています。