plankton-code-quality

Automated code formatting and linting on file edits is handled by Plankton through Claude Code hooks, applying language-specific linters across Python, TypeScript, Shell, YAML, JSON, Markdown, and Dockerfile. It routes fixes through a tiered model system to maintain code quality at write time.

Write-time code quality catches style and correctness issues before they enter the codebase by running auto-formatting and linting during file edits. Plankton enforces this using pre-tool hooks that trigger language-specific linters and formatters immediately after edits occur.

Yes, auto-formatting hooks support multi-language projects by applying language-specific linters and formatters across Python, TypeScript, Shell, YAML, JSON, Markdown, and Dockerfile simultaneously during file edits. This ensures consistent code formatting across all supported file types.

Pre-tool hooks protect linter configurations by implementing guardrails that block unsafe changes and prevent tampering. These defensive measures ensure configuration integrity is maintained, preventing edits that could compromise the automated code quality enforcement process.

Tiered fix routing directs simple style issues to fast fixes using Haiku, while routing complex problems to deeper reasoning with Sonnet or Opus. This system ensures efficient resolution of code quality issues by matching the fix complexity to the appropriate processing tier.