plankton-code-quality

Format, lint, and fix code edits across multiple languages via PostToolUse hooks.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/mitul-bhatia/Vibes --skill plankton-code-quality-mitul-bhatia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plankton-code-quality
Source: https://github.com/mitul-bhatia/Vibes/tree/main/.github/skills/plankton-code-quality
Command: npx skills add https://github.com/mitul-bhatia/Vibes --skill plankton-code-quality-mitul-bhatia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plankton provides write-time code quality enforcement by running formatters and linters on every file edit through PostToolUse hooks, then delegating fixes to Claude subprocesses to catch violations the agent misses.

Core Features & Use Cases

  • Real-time formatting, linting, and automated fixes during editing
  • Guardrails against config tampering and dependency drift
  • Works across multiple languages and integrates with Claude Code

Quick Start

Install Plankton in your project and enable the PostToolUse hooks to start enforcing write-time code quality.

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 code quality automatically during file edits?

Automated code quality enforcement runs formatters and linters on every file edit using PostToolUse hooks, then spawns Claude subprocesses to apply fixes for violations the agent misses.

What is write-time linting and how does it work with Claude Code?

Write-time linting automatically formats and fixes code during editing. It integrates with Claude Code via PostToolUse hooks to orchestrate language-specific linters and spawn subprocesses that apply real-time fixes.

Does this automated formatting support Python, TypeScript, and Dockerfiles?

Automated formatting and linting supports Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, and Dockerfiles, applying real-time fixes across these languages during every file edit.

How do I set up real-time linting hooks to start enforcing code quality?

To set up real-time linting, install Plankton in your project and enable the PostToolUse hooks to start enforcing write-time code quality across your supported languages.

What's the best way to prevent config tampering and dependency drift during development?

Write-time code quality enforcement provides built-in guardrails against config tampering and dependency drift by running automated checks on every file edit through PostToolUse hooks.

Why does my code quality enforcement not catch every linting violation?

Code quality enforcement catches most violations using language-specific linters, but delegates complex missed violations to Claude subprocesses that spawn to apply additional fixes automatically.