plankton-code-quality

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

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill plankton-code-quality-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plankton-code-quality
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/plankton-code-quality
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill plankton-code-quality-freedom909

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, and AI agents may even modify linter configs to bypass rules instead of fixing code. This Skill enforces formatting and linting on every file edit, automatically fixing violations before they reach your repository. ## Core Features & Use Cases - Three-Phase Hook Pipeline: Auto-formats files 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 errors). - Config Tamper Protection: PreToolUse hooks block edits to linter configs like .ruff.toml and biome.json, while a Stop hook detects config changes via git diff at session end. - Package Manager Enforcement: Blocks legacy package managers (pip, npm, yarn) and redirects to modern alternatives (uv, bun) via Bash hooks. - Use Case: A team working across Python and TypeScript wants every AI-assisted edit automatically formatted with ruff and biome, with unfixable violations delegated to a subprocess so the main agent only sees issues that truly need attention. ## 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?▼

Install Plankton's hooks into your project's .claude directory along with the linter configs. The PostToolUse hook runs formatters like ruff and biome on every edit, then delegates remaining violations to a Claude subprocess for automatic fixes.

What linters does Plankton support for Python and TypeScript?▼

Python uses ruff for formatting and linting, with optional ty, vulture, and bandit. TypeScript and JavaScript use biome as the primary tool, with optional oxlint, semgrep, and knip for dead export detection.

Can Plankton prevent AI agents from modifying linter configs?▼

Yes, Plankton blocks edits to protected config files like .ruff.toml and biome.json through a PreToolUse hook. A Stop hook also runs git diff at session end to detect any config changes that slipped through.

Does Plankton work alongside other Claude Code plugins like ECC?▼

Plankton and ECC are complementary but may conflict on JS/TS formatting since ECC's Prettier hook overlaps with Plankton's biome. Disable ECC's Prettier PostToolUse hook when using Plankton, and both can coexist on different file types.

How do I skip the subprocess fix phase in Plankton hooks?▼

Set the environment variable HOOK_SKIP_SUBPROCESS=1 to bypass Phase 3 delegation and report violations directly. You can also set subprocess_delegation to false in the hooks config.json for a persistent change.