plankton-code-quality

Name: plankton-code-quality
Availability: InStock
Author: cescrafli

Format, lint, and fix code on file edits across multiple languages.

Updated Mar 26, 2026

Search Tags:#automation #linting #formatting #hooks #claude #code-quality #plankton

Ready to run

npx skills add https://github.com/cescrafli/compyrasion --skill plankton-code-quality-cescrafli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plankton-code-quality
Source: https://github.com/cescrafli/compyrasion/tree/main/skills/plankton-code-quality
Command: npx skills add https://github.com/cescrafli/compyrasion --skill plankton-code-quality-cescrafli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plankton code quality enforcement reduces manual formatting and linting toil by applying write-time checks during file edits, catching issues before they enter the codebase.

Core Features & Use Cases

Auto-formatting, linting, and fixes executed on every file edit via Plankton hooks and Claude Code integration.
Multi-language support: Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, Dockerfile.
Guardrails for config files and per-project integration to ensure consistent code quality across teams.

Quick Start

Install and run Claude Code with Plankton hooks to format, lint, and fix violations 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 automate code formatting and linting during file edits?▼

Automating code formatting and linting during file edits is achieved by integrating PostToolUse hooks with Claude Code, executing a three-phase workflow of auto-format, violation collection, and Claude-based fixes on every save.

Can I enforce write-time code quality across multiple languages like Python and TypeScript?▼

Yes, write-time code quality enforcement supports multiple languages including Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, and Dockerfile by applying per-project linter integrations like ruff and biome.

What is the best way to integrate pre-tool-use protections for code quality hooks?▼

The best way to integrate pre-tool-use protections is configuring per-project guardrails for config files alongside Plankton hooks, ensuring deterministic formatting and linting tasks execute safely before Claude-based fixes.

Do I need specific linters installed to use write-time auto fixes?▼

Yes, you need per-project integration with specific linters such as ruff, biome, shfmt, taplo, and markdownlint to enable deterministic auto-formatting, violation collection, and automated fixes during file edits.

Why use a three-phase workflow for code quality enforcement instead of standard linting?▼

A three-phase workflow separates auto-format, violation collection, and Claude-based fixes to apply deterministic tasks via hooks first, reducing manual linting toil and catching issues before they enter the codebase.

Does Plankton code quality enforcement work with Claude Code hooks?▼

Yes, Plankton code quality enforcement integrates directly with Claude Code via PostToolUse hooks, applying formatting, linting, and fixes automatically on every file edit across supported languages.