plankton-code-quality

Run formatters and linters on every file edit with Claude subprocess remediation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Maelwalser/claude-config --skill plankton-code-quality-maelwalser
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plankton-code-quality
Source: https://github.com/Maelwalser/claude-config/tree/main/skills/plankton-code-quality
Command: npx skills add https://github.com/Maelwalser/claude-config --skill plankton-code-quality-maelwalser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plankton eliminates noisy, post-commit linting by enforcing formatting and linting immediately on every file edit, and it prevents agents from bypassing quality rules by tampering with linter configs.

Core Features & Use Cases

  • Write-time formatting and linting: Runs formatters and linters on each file edit to fix style and surface violations early.
  • Claude-powered remediation: Spawns isolated Claude subprocesses to generate fixes for violations that automated formatters cannot resolve and reruns verification.
  • Config protection and package manager enforcement: Guards linter config files against unauthorized edits and blocks legacy package manager usage during edits.
  • Use Case: A developer iterating on Python and TypeScript files receives near-instant formatting, machine-suggested fixes for complex violations, and automated verification before the main agent sees any remaining issues.

Quick Start

Run the Plankton hooks in your project directory to enable automatic formatting, linting, and Claude-powered fix delegation on every file edit.

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 write-time code formatting and linting on every file edit?▼

Write-time code formatting and linting on every file edit is enforced by running PreToolUse and PostToolUse hooks that automatically execute installed linters and formatters on edited source files to fix style and surface violations early.

Can AI agents automatically fix unresolved linting violations during development?▼

AI agents can automatically fix unresolved linting violations by spawning isolated Claude subprocesses with tiered model routing and configurable timeouts to generate fixes, followed by automated verification loops before the main agent sees remaining issues.

How do I prevent agents from bypassing code quality rules by tampering with linter configs?▼

To prevent agents from bypassing code quality rules by tampering with linter configs, you can enable protected linter config guards that block unauthorized edits to configuration files and enforce package manager rules during file edits.

Does write-time linting work with multi-language repositories containing Python and TypeScript?▼

Write-time linting works with multi-language repositories containing Python and TypeScript by detecting file edits across different languages and applying the appropriate installed linters and formatters during the development session.

What is the difference between write-time linting and post-commit linting?▼

Write-time linting eliminates noisy post-commit linting by running formatters and linters immediately on each file edit, surfacing violations early and using Claude subprocesses to auto-fix complex issues before they reach the main agent.