plankton-code-quality

You can automate code formatting and lint checks during Claude Code edits by using Plankton PostToolUse hooks, which trigger automatically on file edits to apply formatting and run lint checks in real time.

The Plankton hook supports real-time linting for multi-language projects including Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, and Dockerfile, routing violations to appropriate language-specific linters like Ruff and Biome.

The multi-stage repair workflow routes code violations to Haiku, Sonnet, and Opus model tiers sequentially, using a Claude subprocess to fix violations the agent missed and verifying repairs by re-executing formatting and lint checks.

You need language-specific linters like Ruff, Biome, and markdownlint configured in your project to detect and propose repairs, relying on Plankton configuration to route and verify fixes during Claude Code editing sessions.

You can silently fix lint violations automatically after file edits by integrating Plankton hooks with Claude Code, which seamlessly applies formatting and repairs through a Claude subprocess without manual intervention, independent of your specific editor.

Limitations include dependency on Plankton configuration and external linters, and potential overhead from routing complex violations through Haiku, Sonnet, and Opus model tiers for real-time repair and verification during every file edit.