Guide 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
Rust code review guidelines for Coglet
Cog architecture and cross-cutting review guidelines
| name | python-review |
| description | Python code review guidelines for the Cog SDK |
This project uses Python for the SDK (python/cog/) which defines the predictor
interface, type system, and HTTP/queue server.
ruff handles pycodestyle (E), Pyflakes (F), isort (I), warnings (W), bandit (S), bugbear (B), and annotations (ANN). Don't flag issues these would catch.
Type annotations
typing_extensions for backward compatibilityAny where a concrete type is possibleCompatibility
from __future__ import annotations if using newer annotation syntaxError handling
except: or except Exception: that swallows everythingAsync patterns
Predictor interface
base_predictor.py is the core interface -- changes here affect all userstypes.py defines input/output types -- check backward compatibilitypython/cog/server/ handles HTTP -- watch for request handling bugsTesting