plankton-code-quality

Auto-formatting and linting on every file edit is achieved by running Plankton hooks that trigger formatters and linters across Python, TypeScript, Shell, YAML, Markdown, JSON, TOML, and Dockerfile formats. A three-phase workflow formats code, collects violations, delegates fixes to Claude, and re-verifies results.

Enforcing consistent code style during rapid development is done through write-time hooks that automatically format, lint, and apply fixes as you edit. This layered workflow reduces drift and rework by delegating complex violations to Claude-powered fixes and re-verifying clean results.

Automated code quality enforcement works with TypeScript and Python, alongside Shell, YAML, Markdown, JSON, TOML, and Dockerfile formats. Plankton hooks run formatters and linters on every file edit across these languages to ensure consistent style.

Using Claude to automatically fix linting violations is supported through a layered fix workflow. After deterministic Phase 1 formatting and Phase 2 violation reporting, the workflow delegates fixes to Claude and re-verifies the code to ensure clean results.

Preventing linter configuration modifications during automated fixes is handled by built-in defensive measures within the Plankton hooks. These measures guard linter configurations while the three-phase workflow formats, reports violations, and applies Claude-powered fixes.

Auto-formatting runs in multiple phases because the workflow separates deterministic Phase 1 formatting from Phase 2 violation reporting before delegating fixes to Claude. This layered approach ensures that automated fixes are re-verified for clean results rather than applied blindly.