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.
Python code review guidelines for the Cog SDK
Rust code review guidelines for Coglet
Cog architecture and cross-cutting review guidelines
| name | go-review |
| description | Go code review guidelines for the Cog codebase |
This project uses Go for the CLI (cmd/cog/, pkg/) and support tooling (tools/).
golangci-lint runs errcheck, gocritic, gosec, govet, ineffassign, misspell, revive, staticcheck, and unused. Don't flag issues these would catch.
Error handling
pkg/errors.CodedError with error codesfmt.Errorf("failed") with no %w)Imports
github.com/replicate/cog/pkg/...)Testing
testify/require for fatal assertions and testify/assert for non-fatalif checks with t.Fatal/t.ErrorfEqual, Contains, NoError) over True/FalseConcurrency
Docker/container patterns
pkg/dockerfile/ -- template injection risksArchitecture
pkg/cli/, business logic in pkg/pkg/config/