Workspace-specific Rust rules that override common habits: panic instead of dummy or no-op fallbacks, never catch a panic outside tests, enums over unclear bool parameters, no wildcard match arms, dependencies managed in the workspace Cargo.toml, 2024 edition, zero warnings and clippy lints. Read before writing or editing Rust (.rs) code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Cargo.toml.panic! macro instead of falling back to meaningless dummy values or no-op implementations.catch_unwind, a task is joined through wado_host::sync::joined rather than its JoinError turned into an error value, and a thread's panic is resumed where it is joined. Tests may catch one.enum rather than a bool where the call site would not say what the flag means. f(x, true) makes the reader open f, and f(x, Mode::Strict) does not.2024 edition.mise run clippy runs -D warnings, so any warning or lint fails it.crate:: or super:: path goes in a use item at the top of the module; where the item is read, write its name. use crate::elaborator::sem::Ty; then Ty, never crate::elaborator::sem::Ty inline. Alias a collision (use crate::ast::Ty as AstTy;) rather than spelling the path out. A hook refuses an edit that writes one inline, and mise run check-rust-paths gates the rest._ => ...) unless absolutely necessary.아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Measure Wado's performance or the size of the Wasm it generates, and refresh the benchmark/ and wasm-size/ README files. Use for any benchmarking or size-measurement request, whichever benchmark it names.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Measure how long GitHub Actions jobs and steps took across past runs, and find the pull request that made CI slower. Use for any question about CI duration, a slow job, or when CI got slow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
How to answer code review feedback — a human reviewer, CodeRabbit, or any review bot. Verify the findings, report the classes they are instances of to the user before fixing, then fix the class rather than the sites named. Put design decisions to the user, then run /distill. Invoke when responding to review comments on a pull request, or to the findings of a /code-review run.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Investigate and improve code coverage for the wado-compiler crate. Use for any question about what the tests do and do not reach, dead code included.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review the branch with /code-review at high, then answer the findings with /code-review-response.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use rust-gdb to inspect variables and step through code without modifying it. Prefer it over print debugging for any investigation into what the compiler is actually doing (lldb is unavailable on Claude Code Web).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.