plankton-code-quality

Enforces write-time code quality via hooks that auto-format, lint, and delegate fixes to Claude subprocesses.

1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/ibytechaos/claude --skill plankton-code-quality-ibytechaos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plankton-code-quality
Source: https://github.com/ibytechaos/claude/tree/main/plugins/everything-claude-code/skills/plankton-code-quality
Command: npx skills add https://github.com/ibytechaos/claude --skill plankton-code-quality-ibytechaos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code quality issues are often caught too late—at commit time or in CI—forcing costly rework. This Skill enforces formatting and linting on every file edit through Claude Code hooks, automatically fixing violations before they accumulate. ## Core Features & Use Cases - Three-Phase Enforcement: Auto-formats silently, collects remaining violations as structured JSON, then spawns Claude subprocesses to fix them with tiered model routing (Haiku for style, Sonnet for logic, Opus for type issues). - Config Tamper Protection: PreToolUse hooks block edits to linter configs like .ruff.toml and biome.json, preventing agents from disabling rules instead of fixing code. - Package Manager Enforcement: Blocks legacy package managers (pip, npm, yarn) in favor of uv and bun via Bash hooks. - Use Case: A team working across Python, TypeScript, and Shell wants every AI-assisted edit automatically formatted with ruff and biome, with unfixable violations delegated to a Claude subprocess and only unresolved issues surfaced to the main agent. ## Quick Start Set up Plankton hooks in my project so every file edit is automatically formatted and linted with violations fixed by Claude subprocesses.

Frequently Asked Questions about plankton-code-quality

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

FAQPage Schema
How do I automatically lint and format code on every file edit in Claude Code?

Install Plankton's hooks by copying its .claude/hooks directory and settings.json into your project. The multi_linter.sh PostToolUse hook then runs formatters and linters on every edit, fixing most issues silently.

How does Plankton decide which Claude model fixes a lint violation?

Plankton routes violations by complexity: Haiku handles formatting and style codes with a 120s timeout, Sonnet handles complexity and refactoring issues with 300s, and Opus handles type system problems with 600s.

Can Plankton stop an AI agent from modifying linter config files?

Yes. A PreToolUse hook blocks edits to protected configs like .ruff.toml and biome.json before they happen, and a Stop hook detects config changes via git diff at session end.

Does Plankton work alongside other Claude Code quality plugins?

Yes, but avoid overlapping hooks. For example, disable a Prettier PostToolUse hook when using Plankton's biome formatter on JS/TS files, while letting both coexist on different file types.

How do I skip the Claude subprocess fixing phase in Plankton?

Set the environment variable HOOK_SKIP_SUBPROCESS=1 to skip Phase 3 and report violations directly, or set subprocess_delegation to false in the hooks config.json.