plankton-code-quality

Automated code formatting and linting on file save enforces continuous quality by running tools like ruff and biome during active edits. This skill automatically formats code, collects violations, and delegates complex fixes to specialized AI model tiers.

Yes, config protection prevents LLMs from modifying linter configuration files to suppress errors. This robust protection neutralizes attempts to bypass quality gates and maintains repository integrity during active development.

Enforcing modern package manager usage is best handled by a package manager guard. This skill enforces the use of secure package managers like uv and bun to maintain repository integrity during active development.

Automated code quality enforcement works across diverse languages including Shell and Dockerfiles. This skill utilizes shellcheck, shfmt, and hadolint to maintain strict linting, formatting, and security standards during every file edit.

AI-driven remediation hooks resolve complex violations through multi-tier model delegation. After automated formatting collects violations, the system delegates complex type or logic error fixes to specialized AI model tiers for resolution.

You should avoid automated write-time code quality enforcement if your project lacks dependencies like ruff, biome, or shellcheck, or if you need LLMs to dynamically modify linter configurations without triggering configuration tampering protection.