plankton-code-quality

Automated write-time enforcement runs auto-formatting and linting on every file edit across Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, and Dockerfile. It collects violations and routes fixes to model tiers based on violation complexity.

Yes, pre-tool hooks prevent configuration tampering and enforce package-manager rules during write-time code quality checks. This governance layer ensures consistent quality enforcement across languages without manual oversight.

Tiered fix routing sends collected linting violations to different model tiers based on complexity: Haiku for simple fixes, Sonnet for moderate changes, and Opus for deep modifications. This optimizes processing efficiency for auto-formatting workflows.

Write-time enforcement applies auto-formatting and linting across multi-language projects including Python and TypeScript. It implements phases for pre-format, violation collection, and model delegation to maintain consistent quality across languages.

Yes, automated write-time code quality enforcement supports YAML, TOML, and Dockerfile formats alongside Python, TypeScript, Shell, JSON, and Markdown. Cross-language support applies formatting and linting on every file edit across all supported formats.

Pre-format and violation collection phases structure the enforcement workflow: pre-format standardizes style, violation collection identifies remaining issues, and model delegation routes fixes by complexity. This phased approach ensures thorough quality checks on every edit.