plankton-code-quality

Automates write-time code quality enforcement via Plankton hooks and Claude subprocesses for linting/formats across languages.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/GGEdu/claude-god-mode-template --skill plankton-code-quality-ggedu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plankton-code-quality
Source: https://github.com/GGEdu/claude-god-mode-template/tree/main/skills/plankton-code-quality
Command: npx skills add https://github.com/GGEdu/claude-god-mode-template --skill plankton-code-quality-ggedu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code quality tends to degrade during rapid edits. Plankton Code Quality Skill enforces write-time quality by running a suite of formatters and linters on every file edit and then using Claude subprocesses to apply fixes when violations are detected, ensuring consistent quality without slowing development.

Core Features & Use Cases

  • Automatic formatting and linting across multiple languages (Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, Dockerfile) using pluggable formatters and linters.
  • Safe automated remediation via Claude subprocess routing, with tiered model routing for simple to complex fixes.
  • Guardrails for config protection and deterministic outcomes, with audit-friendly hooks and memory of decisions.

Quick Start

Install Plankton hooks in your project and run Claude Code to start enforcing write-time quality checks.

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 on every file edit is handled by executing Plankton hooks that trigger formatters and linters across Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, and Dockerfile projects. Claude subprocesses then apply fixes when violations are detected.

What is write-time code quality enforcement and how does it work?

Write-time code quality enforcement runs formatters, linters, and safety checks immediately after file edits using PostToolUse hooks. It routes violations to Claude subprocesses for tiered model remediation, ensuring deterministic outcomes and auditability without slowing development.

Can I use automated linting fixes with Python and TypeScript projects?

Yes, automated linting fixes support Python and TypeScript projects, alongside Shell, YAML, JSON, TOML, Markdown, and Dockerfile. Pluggable formatters and linters execute on file edits, routing violations to Claude subprocesses for safe, tiered remediation.

What's the best way to prevent code quality degradation during rapid edits?

Preventing code quality degradation during rapid edits requires strict guardrails and pre-configured PostToolUse hooks. This approach applies auto-formatting and linting on every file edit, using model-tier routing for deterministic remediation and audit-friendly memory of decisions.

Do I need pre-configured linters and formatters to use automated code fixes?

Yes, pre-configured linters and formatters are required to ensure deterministic remediation. The system depends on pluggable tooling and strict guardrails, including PostToolUse hooks and model-tier routing, to execute safe automated fixes via Claude subprocesses.

How do I set up write-time code quality checks in my project?

To set up write-time code quality checks, install Plankton hooks in your project and run Claude Code. This activates PostToolUse hooks to apply auto-formatting, linting, and safety checks across multiple languages on every file edit.