ワンクリックで
testing
Apply when writing or running tests, or updating insta snapshots, in this repo.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Apply when writing or running tests, or updating insta snapshots, in this repo.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Apply for build/test/lint, dependency or feature changes, and editing Cargo.toml or .cargo config in this repo.
Apply when starting work, branching, committing, opening/reading PRs, reading issues, or checking CI — the git + GitHub (gh) workflow.
Apply when creating or tracking a GitHub issue, or planning multi-step work — the issue template and the task convergence loop.
Apply when writing, editing, reviewing, or refactoring ANY code in this repo — coding-behavior rules to avoid overcomplication and make surgical, verifiable changes.
Apply when changing the REST API surface — actix handlers, utoipa annotations, or request/response types under server/.
Apply when editing .proto files or the generated protobuf types (src/pbs/*) in this repo.
| name | testing |
| description | Apply when writing or running tests, or updating insta snapshots, in this repo. |
cargo test (CI default) or cargo test --all-features. Prefer red-green (see karpathy-principle).cargo insta review (or cargo insta accept). Never blindly accept.tests/data/**, *.bin, and named snaps in .gitattributes); most .snap files are plain git. Have git lfs installed so fixtures resolve.rstest for parameterized tests/fixtures; tracing-test to assert on logs; temp_testdir/tempfile for scratch dirs; pretty_assertions for diffs.