plankton-code-quality

Run formatters and linters on every file edit across multiple languages.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/TruCol270/salty-pickle --skill plankton-code-quality-trucol270
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plankton-code-quality
Source: https://github.com/TruCol270/salty-pickle/tree/main/.claude-skills/plankton-code-quality
Command: npx skills add https://github.com/TruCol270/salty-pickle --skill plankton-code-quality-trucol270

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plankton automates write-time code quality enforcement by running formatters, linters, and Claude-driven fixes on every file edit, helping teams maintain consistent style and reduce drift.

Core Features & Use Cases

  • Automatic formatting and linting on every edit across multiple languages (Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, Dockerfile)
  • Tiered fix routing (Haiku, Sonnet, Opus) for different complexity levels and repair strategies
  • Defense against config changes that bypass lint rules and ensure a stable development workflow

Quick Start

Install the Plankton hooks and start Claude Code to enable write-time quality enforcement.

Frequently Asked Questions about plankton-code-quality

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

FAQPage Schema
How do I automate code formatting and linting on every file edit in Claude Code?

Automated write-time code quality enforcement runs formatters and linters on every file edit by installing Plankton hooks into Claude Code, preventing drift and regressions automatically.

Can I run linters and formatters across multiple languages like Python and TypeScript simultaneously?

Yes, write-time code quality enforcement applies formatting and linting across Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, and Dockerfile formats by routing fixes through Claude subprocesses.

What is tiered fix routing for code linting violations?

Tiered fix routing processes linting violations by routing fixes through different model tiers like Haiku, Sonnet, and Opus to match repair complexity and strategy.

How do I prevent config changes from bypassing lint rules in my development workflow?

Write-time code quality enforcement defends against config changes that bypass lint rules by running Plankton hooks and Claude subprocesses to collect violations and route fixes consistently.

Does Plankton work with ruff and biome for formatting and fixing code?

Yes, Plankton executes formatters and linters including ruff, biome, shfmt, and markdownlint through Claude subprocesses to format, lint, and fix code during edits.

What do I need to set up before enabling write-time code quality with Plankton?

To enable write-time code quality, you need to install the Plankton hooks and start Claude Code to allow subprocesses to execute formatters and collect violations on file edits.