plankton-code-quality

Automated code quality enforcement runs multi-phase linting and formatting via PostToolUse hooks on every file edit. It formats code with tools like Ruff and Biome, collects violations, and delegates complex fixes to specialized AI model tiers for strict adherence to project standards.

To stop AI agents from suppressing errors, use a code quality enforcement system with built-in config protection. This prevents agents from modifying linter configuration files, ensuring violations are resolved through proper formatting and remediation rather than rule suppression.

Yes, Ruff and Biome can be used together for automated code formatting and violation fixes. Ruff handles Python linting and formatting, while Biome manages TypeScript, operating in tandem to collect violations and delegate remaining logic errors to AI-powered remediation.

The best way to run tiered AI model fixes for complex code violations is through a PostToolUse hook system. It automatically formats code first, then delegates any remaining unresolved logic errors to specialized subprocess AI model tiers before the main agent views them.

Yes, automated linting works across Shell scripts and Dockerfiles alongside Python and TypeScript. The enforcement system utilizes shellcheck, shfmt, and hadolint to maintain strict code quality standards and format adherence across multiple programming languages and infrastructure files.

Yes, you need to install required linters before activating write-time code quality enforcement. The system depends on external tools like ruff, biome, shellcheck, yamllint, and hadolint to perform automated formatting and collect violations within your project directory.