plankton-code-quality

Automated write-time code quality enforces formatting and linting on every file edit by running tools like ruff, biome, and shfmt through Plankton post-tool hooks integrated with Claude Code, catching style violations before they enter a commit.

Write-time linting supports Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, and Dockerfile by applying language-specific linters and formatters such as ruff, biome, shfmt, yamllint, hadolint, taplo, and markdownlint across all edits.

Write-time code quality collects violations from standard linters and defers complex fixes to a Claude-driven workflow, ensuring simple formatting is auto-corrected while intricate issues are resolved contextually.

Yes, Plankton post-tool hooks and Claude Code integration are required to activate write-time quality enforcement, enabling formatters and linters to run automatically as you edit files.

Write-time hooks include defense and guardrails that protect linter configurations and enforce package-manager rules, preventing breaking changes to your project's quality standards.

The best way to run ruff and biome automatically is by using Plankton hooks with Claude Code to trigger write-time code quality enforcement on every file edit across Python and TypeScript projects.