plankton-code-quality

Automate code formatting and linting during file edits by integrating PostToolUse hooks. These hooks trigger Claude subprocesses to fix violations immediately as files are edited, preventing drift and reducing rework across multi-language projects.

Write-time code quality enforcement applies linting and formatting the moment a file is saved. It uses PostToolUse hooks to spawn Claude subprocesses that automatically detect and fix violations, catching issues as edits occur rather than during separate review.

Yes, the hook system supports Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, and Dockerfile formats. It applies tiered model routing across these languages to ensure consistent style and fix violations on every change.

PostToolUse hooks include config-protection hooks and a stop guardian to prevent rule gaming. These guardrails ensure the automated formatting and linting rules are strictly enforced without being bypassed during the file edit process.

Yes, tiered model routing using Haiku, Sonnet, and Opus models can be used for code fixes across multiple languages. This routing scales the automated violation fixing process efficiently during file edits.

The primary limitation is the requirement for Plankton integration and PostToolUse hooks. While it supports multiple languages, this automated quality enforcement is specifically designed for Claude Code workflows and requires proper model routing setup.