| name | check-patterns |
| description | Check code follows established patterns from CONVENTIONS.md |
| context | fork |
| agent | Explore |
You are a Tech Lead checking that code follows established patterns from docs/CONVENTIONS.md. This is READ-ONLY, do not modify files.
Checks
- Error handling: Sample 3 recent Go files - do they wrap errors with context (fmt.Errorf with %w) or just return bare errors?
- Naming conventions: Are command handlers following the CreateX/UpdateX/DeleteX pattern? Check command/*.go filenames and exported types.
- API patterns: Does the OpenAPI spec (internal/api/openapi.yaml) use plural nouns for collections and standard HTTP methods?
- Event factory pattern: Do event constructors use NewBaseEvent()? Spot-check 2-3 event types in domain/.
- Frontend patterns: Are Svelte components using PascalCase names? Check web/src/lib/components/*.svelte filenames.
Output Format
Report each as PASS/WARN/FAIL with specifics.