plankton-code-quality

Run formatters and linters on every Claude Code file edit and auto-remediate violations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents agents from shipping code that violates formatting, linting, or configuration standards by enforcing write-time quality checks and auto-remediation during file edits.

Core Features & Use Cases

  • Write-time formatting and linting: Runs formatters and linters on every file edit to keep code consistent continuously, not just at commit time.
  • LLM-assisted violation fixes with verification: Delegates remaining issues to tiered Claude subprocesses, then re-runs checks to confirm the workspace is clean.
  • Config tamper protection: Blocks or detects attempts to “game” quality by modifying linter/config files so fixes are real, not suppressed.
  • Cross-language coverage: Supports Python, TypeScript/JavaScript, Shell, YAML, JSON, TOML, Markdown, and Dockerfile quality tooling.

Quick Start

Ask Claude Code to run in the Plankton skill directory so the configured hooks in .claude/settings.json automatically enforce formatting, linting, and auto-fixes on each 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 enforce code quality and linting automatically when an AI agent edits files?

Write-time code quality enforcement runs formatters and linters on every agent file edit, automatically remediating remaining violations to keep multi-language codebases standards-compliant continuously.

Can I auto-fix linting violations across Python, TypeScript, and YAML in the same workflow?

Yes, cross-language auto-fix workflows target Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, and Dockerfile, running formatters and linters across all supported languages on every edit.

How do LLM-assisted linter fixes with verification work?

LLM-assisted linter fixes delegate remaining violations to tiered Claude subprocesses, then re-run checks to verify the workspace is clean before exiting, ensuring fixes are confirmed and not suppressed.

How to prevent agents from gaming code quality checks by modifying linter config files?

Config tamper protection blocks or detects attempts to modify linter and configuration files during edits, ensuring quality fixes are real and not suppressed by agent config manipulation.

What is a write-time hook pipeline for formatting and auto-remediation?

A write-time hook pipeline is a three-phase process that formats silently, collects structured linter violations, delegates fixes via tiered model subprocesses, then re-verifies and exits clean only when resolved.

Does multi-language code quality enforcement work without manual linting commands?

Yes, configured hooks in the settings automatically enforce formatting, linting, and auto-fixes on each edit without manual commands, keeping code consistent continuously rather than just at commit time.