go-review
Go review guidelines
This project uses Go for the CLI (cmd/cog/, pkg/) and support tooling (tools/).
What linters already catch (skip these)
golangci-lint runs errcheck, gocritic, gosec, govet, ineffassign, misspell, revive, staticcheck, and unused. Don't flag issues these would catch.
What to look for
Error handling
- Errors returned but not checked or silently discarded
- User-facing errors should use
pkg/errors.CodedErrorwith error codes - Generic error wrapping that loses context (
fmt.Errorf("failed")with no%w)
Imports
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.
6python-review
Python code review guidelines for the Cog SDK
5cog-review
Cog architecture and cross-cutting review guidelines
5release-cog
Guide and automate the Cog release process
5rust-review
Rust code review guidelines for Coglet
5