What problem does it solve? Reviewing code in GMT Temporal projects requires checking Temporal-specific rules that generic review checklists miss, such as banning Date objects, wrapping Temporal parsing in try-catch, and avoiding plain/zoned type mixing. ## Core Features & Use Cases - Canonical Checklist Enforcement: Defers to a single source-of-truth checklist covering API contracts, architecture, tests, documentation, and reviewer tone. - Pattern Recognition Examples: Provides worked examples of common violations including missing try-catch around Temporal.PlainDate.from, new Date() usage, and plain/zoned mixing. - Test Convention Guidance: Flags incorrect it.each array syntax and shows the required template literal form plus pre-built error-path mocks. - Use Case: When reviewing a pull request in the gmt, gmt-oxlint, gmt-eslint, or gmt-biome packages, apply this skill to catch Temporal error-handling gaps and test convention violations before merge. ## Quick Start Review this pull request in the gmt package using the GMT Temporal code review checklist and flag any Date object usage or missing error handling.