plankton-code-quality

Enforce write-time code quality with Plankton via PostToolUse hooks.

1|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/aleonsa/claude-config --skill plankton-code-quality
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plankton-code-quality
Source: https://github.com/aleonsa/claude-config/tree/main/claude/skills/plankton-code-quality
Command: npx skills add https://github.com/aleonsa/claude-config --skill plankton-code-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates code formatting, linting, and quality checks directly within the development workflow, preventing code quality issues before they become larger problems.

Core Features & Use Cases

  • Write-time Enforcement: Runs formatters and linters on every file edit via PostToolUse hooks.
  • Automated Fixes: Attempts to fix violations automatically, escalating complex issues to Claude.
  • Config Protection: Prevents LLMs from disabling linter rules to bypass fixes.
  • Package Manager Enforcement: Blocks legacy package managers in favor of modern alternatives.
  • Use Case: Ensure all Python, TypeScript, Shell, and other code files are consistently formatted and linted as you type, with automatic corrections for common issues.

Quick Start

Run the plankton code quality skill to automatically format and lint the current project's files.

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?

Automated code formatting and linting runs on every file edit through PostToolUse hooks, applying formatters and linters directly within the development workflow to prevent quality issues as you type.

Can I enforce consistent code quality across Python, TypeScript, and YAML files?

Yes, consistent code quality is enforced across Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, and Dockerfile by running formatters and linters automatically whenever files are modified.

How do I stop LLMs from modifying linter configurations to bypass rules?

Config protection prevents LLMs from modifying linter configurations to bypass rules, ensuring automated fixes are applied properly and quality settings remain secure from tampering.

Does this code quality tool block legacy package managers in favor of modern alternatives?

Yes, package manager enforcement blocks legacy tools in favor of modern alternatives, ensuring dependency management follows current standards across the development workflow.

What is write-time code quality enforcement?

Write-time code quality enforcement runs formatters, linters, and automated fixes during file editing via PostToolUse hooks, preventing quality issues before they become larger problems rather than catching them later.