plankton-code-quality

Enforces write-time code quality via hook-driven formatting, linting, and model-routed fixes.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Femad-6/my-skills --skill plankton-code-quality-femad-6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plankton-code-quality
Source: https://github.com/Femad-6/my-skills/tree/main/.github/skills/plankton-code-quality
Command: npx skills add https://github.com/Femad-6/my-skills --skill plankton-code-quality-femad-6

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 PostToolUse hooks, automatically fixing violations before they accumulate. ## Core Features & Use Cases - Three-Phase Enforcement: Auto-formats files silently, collects remaining violations as structured JSON, then delegates fixes to Claude subprocesses routed by complexity (Haiku for style, Sonnet for logic, Opus for type errors). - Config Tamper Protection: Blocks edits to linter configs like .ruff.toml and biome.json via PreToolUse hooks, preventing agents from disabling rules instead of fixing code. - Package Manager Enforcement: Blocks legacy package managers (pip, npm, yarn) and redirects to uv and bun. - Use Case: A team working across Python, TypeScript, Shell, and YAML wants every AI-assisted edit automatically formatted and linted, with only unfixable violations 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 model-tiered 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 set up automatic linting on every file edit in Claude Code?

Copy the .claude/hooks directory and hook configuration from settings.json into your project, then install the linters for your languages such as ruff and biome. The PostToolUse hooks activate automatically when Claude Code runs in that directory.

How does Plankton route lint fixes to different Claude models?

Plankton routes violations by complexity: Haiku handles formatting and style codes with a 120s timeout, Sonnet handles complexity and refactoring with 300s, and Opus handles type system issues with 600s. Violation counts above the volume threshold auto-escalate to a higher tier.

Can Plankton and ECC hooks run together without conflicts?

Yes, but ECC's Prettier hook may conflict with Plankton's biome formatter on JS/TS files. The recommended resolution is to disable ECC's Prettier PostToolUse hook and let Plankton handle those file types.

How does Plankton prevent agents from modifying linter configs?

A PreToolUse hook blocks edits to protected files like .ruff.toml and biome.json before they happen, and a Stop hook detects config changes via git diff at session end. This prevents agents from disabling rules instead of fixing code.

Which package managers does Plankton block and allow?

Plankton blocks pip, pip3, poetry, pipenv, npm, yarn, and pnpm via a PreToolUse Bash hook, redirecting to uv for Python and bun for JavaScript. Exceptions are allowed for npm audit, npm view, and npm publish.