plankton-code-quality

Integration reference for Plankton (credit: @alxfazio), a write-time code quality enforcement system for Claude Code. Plankton runs formatters and linters on every file edit via PostToolUse hooks, then spawns Claude subprocesses to fix violations the agent didn't catch. Every time Claude Code edits or writes a file, Plankton's multi_linter.sh PostToolUse hook runs: The main agent only sees issues the subprocess couldn't fix. Most quality problems are resolved transparently. LLMs will modify .ruff.toml or biome.json to disable rules rather than fix code. Plankton blocks this with three layers: A PreToolUse hook on Bash blocks legacy package managers: No install command, no plugin config. The hooks in .claude/settings.json are picked up automatically when you run Claude Code in the Plankton directory. To use Plankton hooks in your own project: If running both ECC and Plankton hooks: Plankton's .claude/hooks/config.json controls all behavior: Key settings: Set strict quality behavior: During quality enforcement, flag changes to config files in same iteration: If config is changed to suppress violations, require explicit review before merge.