plankton-code-quality

Automate write-time code quality enforcement by enabling PostToolUse hooks that format, lint, and fix violations as edits occur. This reduces manual review overhead and prevents style drift across multi-language repositories.

Write-time code quality enforcement applies formatting and linting fixes immediately as files are edited. It uses tiered subprocess delegation with timeouts to route fixes, ensuring violations are resolved during active development.

Yes, enforcing auto-formatting and linting requires Plankton setup in your project. You must also configure pre-tool hooks to protect configuration files before the automated formatting process can run.

Maintain consistent style across multi-language repositories by applying supported formatters and linters automatically on every edit. This ensures continuous code quality enforcement across all languages supported by your setup.

Collect and fix code violations by using tiered model routing for fixes, delegating tasks to Haiku, Sonnet, or Opus subprocesses with timeouts. This automatically resolves issues as files are edited.

PostToolUse hooks for code quality automatically format and lint files immediately after edits, reducing manual review overhead. This prevents style drift and ensures violations are fixed at write-time rather than during later stages.