plankton-code-quality

To enforce code quality at write-time, you can use PostToolUse hooks to run formatters and linters on each save, catching and fixing style violations immediately. This automated checking reduces drift and rework.

Automating linting and formatting involves configuring PostToolUse hooks to run tools like ruff and biome on each save. These hooks collect violations and route fixes through tiered models for targeted corrections.

Yes, tiered model routing allows you to delegate linter violations to Haiku, Sonnet, or Opus based on complexity. This generates targeted fixes by matching the model tier to the specific violation.

Yes, multi-language support covers YAML, TOML, Dockerfiles, Shell, and Markdown. It applies formatters like taplo and hadolint through PostToolUse hooks across your entire development workflow.

To prevent config drift, this approach guards linter configurations from being silently disabled or bypassed. It ensures consistent quality enforcement by defending the configs during automated checks.

Before automating code quality, you must configure and install Plankton hooks and associated linters like ruff, biome, and hadolint. This setup provides the end-to-end enforcement required for write-time checks.