plankton-code-quality

You can auto-format and lint code on every edit by using PostToolUse hooks to trigger formatters and linters automatically. This enforces write-time code quality across Python, TypeScript, Shell, YAML, JSON, and Markdown files continuously.

Automatically fixing unfixable linting violations requires delegating remediation to a Claude subprocess with tiered timeouts. The system routes violations by complexity, handling light style fixes and deeper refactors through a verification loop.

Write-time code quality enforcement blocks or detects edits to linter and formatter configuration files. This config tamper protection prevents agents from weakening rules to pass checks instead of actually fixing the code.

Yes, automated formatting and linting hooks apply to Dockerfile and TOML files, alongside TypeScript, Python, Shell, YAML, JSON, and Markdown. The multi-language workflow ensures agents introduce no formatting or type issues across these formats.

Agents may bypass lint rules by editing configuration files to weaken rules rather than fixing code. Config tamper defense detects and blocks these edits, forcing the agent to resolve violations through actual code remediation and verification.