plankton-code-quality

Automates code quality enforcement by running formatters and linters via PostToolUse hooks.

86|21|Updated Feb 9, 2026

Search Tags:#linting #formatting #multi-language #code-quality #gemini #hook-integration #plankton

Ready to run

npx skills add https://github.com/Jamkris/everything-gemini-code --skill plankton-code-quality-jamkris

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plankton-code-quality
Source: https://github.com/Jamkris/everything-gemini-code/tree/main/skills/plankton-code-quality
Command: npx skills add https://github.com/Jamkris/everything-gemini-code --skill plankton-code-quality-jamkris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plankton code quality enforcement catches and fixes style, formatting, and linting issues as you edit, reducing drift and rework by applying automated checks through PostToolUse hooks.

Core Features & Use Cases

PostToolUse hooks for immediate formatting: runs formatters and linters (ruff, biome, shfmt, taplo, markdownlint) on each save to fix or report issues.
Tiered model routing for fixes: routes violations to Haiku, Sonnet, or Opus based on complexity to generate targeted fixes.
Multi-language support: covers Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, and Dockerfile across development workflows.
Defends against config drift: guards linter configs from being silently disabled or bypassed and ensures consistent quality enforcement.

Quick Start

Start Gemini and enable Plankton hooks in your project to begin enforcing write-time code quality.

Frequently Asked Questions about plankton-code-quality

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce code quality at write-time across multiple languages?▼

To enforce code quality at write-time, you can use PostToolUse hooks to run formatters and linters on each save, catching and fixing style violations immediately. This automated checking reduces drift and rework.

How do I automate linting and formatting for Python and TypeScript during development?▼

Automating linting and formatting involves configuring PostToolUse hooks to run tools like ruff and biome on each save. These hooks collect violations and route fixes through tiered models for targeted corrections.

Can I route linter violations to different models based on complexity?▼

Yes, tiered model routing allows you to delegate linter violations to Haiku, Sonnet, or Opus based on complexity. This generates targeted fixes by matching the model tier to the specific violation.

Does this code quality enforcement work with YAML, TOML, and Dockerfiles?▼

Yes, multi-language support covers YAML, TOML, Dockerfiles, Shell, and Markdown. It applies formatters like taplo and hadolint through PostToolUse hooks across your entire development workflow.

How do I prevent linter configs from being silently disabled or bypassed?▼

To prevent config drift, this approach guards linter configurations from being silently disabled or bypassed. It ensures consistent quality enforcement by defending the configs during automated checks.

What do I need to set up before automating code quality enforcement with hooks?▼

Before automating code quality, you must configure and install Plankton hooks and associated linters like ruff, biome, and hadolint. This setup provides the end-to-end enforcement required for write-time checks.