| name | rust-review |
| description | Rust code review guidelines for Coglet |
This project uses Rust for Coglet (crates/), the prediction server that runs
inside Cog containers. It handles HTTP requests, worker process management, and
prediction execution.
clippy runs in CI. cargo-deny audits dependencies for license/advisory issues. Don't flag issues these would catch.
Error handling
thiserror for typed errors in library code, anyhow for application errors.unwrap() or .expect() in non-test code unless the invariant is documented.context() or .with_context() from anyhow, not bare ?Ownership and lifetimes
Async (tokio)
spawn_blocking).await on futures (compiler catches some, but not all logical issues)Safety
unsafe block needs justification and a safety commentArchitecture
crates/coglet/ is the core: HTTP server, worker orchestration, IPCcrates/coglet-python/ is PyO3 bindings for Python predictor integrationinsta -- check if snapshots need updatingDependencies
crates/deny.toml audits themGuide and automate the Cog release process
Use this skill when updating, reviewing, or creating architecture documentation in the architecture/ directory. This includes after refactors, feature additions, component changes, or when auditing docs for accuracy. Use it any time code changes affect how Cog's internals work -- new packages, changed IPC protocols, modified build pipeline, runtime behavior changes. Also use it proactively when reviewing PRs that touch core systems to check whether the architecture docs need updating.
Go code review guidelines for the Cog codebase
Python code review guidelines for the Cog SDK
Cog architecture and cross-cutting review guidelines