plankton-code-quality

Automated code formatting and linting on file edits is handled by running formatters and linters at write time, applying fixes via Claude subprocesses. This enforces quality across Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, and Dockerfile automatically.

Write-time code quality enforcement runs formatters and linters on every file edit, automatically applying fixes through Claude subprocesses. It uses a three-phase architecture: Auto-Format, Collect Violations, and Delegate & Verify to coordinate deterministic fixes across workflows.

Yes, code quality automation supports formatting and linting for Python and TypeScript, alongside Shell, YAML, JSON, TOML, Markdown, and Dockerfile. It coordinates deterministic formatting and fixes across these languages within your project workflows.

Yes, config tampering is prevented using PreToolUse hook protection and Stop hook detection. Package-manager enforcement blocks legacy managers in favor of modern tools, ensuring configurations remain safe and consistent during automated quality enforcement.

The best way to integrate real-time linting is by cloning the enforcement tool into your project and enabling Claude Code hooks. This per-project integration triggers formatters and linters on every edit, applying fixes automatically through subprocesses.

Hooks are needed for code quality enforcement because they trigger formatters and linters automatically at write time, eliminating manual intervention. PreToolUse hooks ensure every file edit is validated and fixed immediately via Claude subprocesses.