python-review
Python review guidelines
This project uses Python for the SDK (python/cog/) which defines the predictor
interface, type system, and HTTP/queue server.
What linters already catch (skip these)
ruff handles pycodestyle (E), Pyflakes (F), isort (I), warnings (W), bandit (S), bugbear (B), and annotations (ANN). Don't flag issues these would catch.
What to look for
Type annotations
- Required on all function signatures
- Use
typing_extensionsfor backward compatibility - Avoid
Anywhere a concrete type is possible - Check that type annotations actually match runtime behavior
More from replicate/cog
updating-architecture-docs
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.
6cog-review
Cog architecture and cross-cutting review guidelines
5go-review
Go code review guidelines for the Cog codebase
5release-cog
Guide and automate the Cog release process
5rust-review
Rust code review guidelines for Coglet
5