plankton-code-quality

Auto-fixing lint and formatting violations on every file edit is handled by Plankton using PostToolUse hooks to run formatters and linters, then delegating remaining violations to a tiered LLM subprocess for remediation.

To stop config tampering that games linter rules, Plankton detects and blocks modifications to formatter and linter configuration files, preventing attempts to bypass quality enforcement during development.

You can enforce multi-language code quality across Python, TypeScript, JavaScript, Shell, YAML, Markdown, Dockerfile, TOML, and JSON using Plankton's automated formatting and linting hooks.

Write-time code quality enforcement is a process that formats and lints files during edits using git hooks, then escalates unresolved violations to tiered LLM subprocesses based on complexity for auto-remediation.

Enforcing approved package managers and blocking legacy tooling is achieved through Plankton's package-manager guardrails, which restrict environment drift by validating tooling on every run.

Auto-formatted files may still have linting violations after edits because standard tools cannot fix complex issues, which Plankton addresses by delegating remaining violations to tiered LLM subprocesses for remediation.