plankton-code-quality

Clone the Plankton repository, install core dependencies like ruff, uv, and jaq, then run Claude Code in that directory. The PostToolUse hooks in .claude/settings.json activate automatically and run formatters and linters on every edit.

Plankton routes violations by complexity: Haiku handles formatting and style codes with a 120s timeout, Sonnet handles complexity and refactoring with 300s, and Opus handles type system issues with 600s. Violations above the volume threshold auto-escalate to a higher tier.

Yes, Plankton uses three layers of config protection: a PreToolUse hook blocks edits to files like .ruff.toml and biome.json, a Stop hook detects config changes via git diff at session end, and a protected files list covers shellcheck, yamllint, and hadolint configs.

Plankton and ECC can coexist, but ECC's Prettier hook may conflict with Plankton's biome formatter on JS/TS files. The recommended resolution is to disable ECC's Prettier PostToolUse hook since Plankton's biome coverage is more comprehensive.

Set the environment variable HOOK_SKIP_SUBPROCESS=1 to skip Phase 3 delegation and report violations directly. You can also set subprocess_delegation to false in .claude/hooks/config.json for a persistent change.