Skip to main content

The Thinking Behind eslint-plugin-repo

ยท One min read
Nick2bad4u
Project Maintainer

eslint-plugin-repo exists to move repository governance checks closer to the developer feedback loop.

Instead of relying only on CI failures after a PR opens, these rules surface policy drift during local linting.

Core philosophyโ€‹

  • Keep rules explicit and narrowly scoped.
  • Prefer actionable diagnostics over vague policy errors.
  • Treat autofix as an assistive capability, not a silent rewrite mechanism.

Why Docusaurus is part of the architectureโ€‹

A rule plugin without durable docs quickly becomes difficult to adopt. The docs site is intentionally split:

  • Rule docs for consumers.
  • Developer docs for maintainers.
  • Generated API docs for type and surface reference.

That split keeps onboarding and long-term maintenance practical.