What problem does it solve? Teams adopting @northguild/gmt need to prevent new Date usage and legacy date-library imports from entering their codebase, but enabling lint rules repo-wide at once can overwhelm legacy-heavy projects with thousands of baseline violations. ## Core Features & Use Cases - CI Lint Integration: Adds ESLint Date-ban rule checks to PR and mainline pipeline steps so violations block merges. - Staged Rollout: Scopes the date-library import ban (moment, dayjs, luxon, date-fns, spacetime) to new or changed paths via flat-config files overrides, then widens coverage as imports are migrated. - Actionable Diagnostics: Keeps rule IDs and file paths clear in CI output, and coordinates Date-ban policy consistently across ESLint, Biome, and Oxlint setups. - Use Case: A repository with hundreds of legacy moment imports enables the import ban only on new packages first, cleans up the baseline incrementally, then expands to full-repo enforcement on the main branch. ## Quick Start Ask the assistant to add a CI lint step that enforces the gmt-eslint Date-ban rules on pull requests with a staged rollout scoped to changed paths.
