plankton-code-quality

Run formatters and linters automatically on every file edit.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of inconsistent code quality, delayed detection of formatting and linting issues, and AI agents bypassing quality rules by modifying linter configurations instead of fixing code, which leads to technical debt and unreliable codebases.

Core Features & Use Cases

  • Write-time quality enforcement: Runs formatters and linters automatically every time a file is edited, catching issues immediately instead of waiting for commit-time checks.
  • AI-powered auto-remediation: Spawns Claude subprocesses to fix complex violations that linters cannot resolve automatically, using tiered model routing to balance speed and accuracy.
  • Config tamper protection: Blocks edits to linter configuration files and detects unauthorized changes at session end to prevent agents from disabling rules to pass checks. Use case: A development team using AI coding assistants can use this Skill to ensure all code edits meet team quality standards without manual review, even when agents are generating or modifying code.

Quick Start

Use the plankton-code-quality skill to automatically enforce code formatting and linting rules on all files you edit in your current project.

Frequently Asked Questions about plankton-code-quality

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically run linters and formatters on every file edit?

Automated write-time code quality enforcement runs formatters and linters automatically on every file edit across Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, and Dockerfile files, catching formatting and linting issues immediately instead of waiting for commit-time checks.

How do I stop AI coding agents from modifying linter configuration files to bypass quality rules?

Config tamper protection blocks edits to linter configuration files during a session and detects unauthorized changes at session end, preventing AI agents from disabling rules to pass checks instead of fixing the actual code.

Can linters automatically fix complex code violations that require deeper analysis?

AI-powered auto-remediation spawns Claude subprocesses to fix complex violations that linters cannot resolve automatically, using tiered model routing to balance speed and accuracy for automated linting violation remediation.

What is the best way to enforce code formatting and linting standards for a team using AI coding assistants?

Write-time quality enforcement ensures all code edits meet team quality standards without manual review by running formatters and linters automatically on every file edit, even when AI agents are generating or modifying code.

Does automated code quality enforcement work with legacy package managers?

Write-time code quality enforcement satisfies requirements for legacy package manager enforcement, applying automated formatting and linting rules to development workflows involving Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, and Dockerfile files.