plankton-code-quality

Topics in the source

• Plankton Code Quality Skill
• When to Use
• How It Works
• Three-Phase Architecture
• What the Main Agent Sees
• Config Protection (Defense Against Rule-Gaming)
• Package Manager Enforcement
• Setup

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. You want automatic formatting and linting on every file edit (not just at commit time) You need defense against agents modifying linter configs to pass instead of fixing code You want tiered model routing for fixes (Haiku for simple style, Sonnet for logic, Opus for types) You work with multiple languages (Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, Dockerfile) Every time Claude Code edits or writes a file, Plankton's multilinter.sh PostToolUse hook runs: | Scenario | Agent sees | Hook exit | |----------|-----------|-----------| | No violations | Nothing | 0 | | All fixed by subprocess | Nothing | 0 | | Violations remain after subprocess | [hook] N violation(s) remain | 2 | | Advisory (duplicates, old tooling) | [hook:advisory] ... | 0 | 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

This is an excerpt. Refer to the complete source and its current requirements.