plankton-code-quality
Write-time code quality enforcement using Plankton — auto-formatting, linting, and Codex-powered fixes on every file edit via hooks.
npx skills add mturac/everything-openai-codex --skill plankton-code-quality --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Plankton Code Quality Skill Integration reference for Plankton (credit: @alxfazio), a write-time code quality enforcement system for OpenAI Codex. Plankton runs formatters and linters on every file edit via PostToolUse hooks, then spawns Codex subprocesses to fix violations the agent didn't catch. ## When to Use - You want automatic formatting and linting on every file edit (not just at commit time) - You need defense against agents modifying linter configs to pass instead of fixing code - You want tiered model routing for fixes (Fast for simple style, Standard for logic, Deep for types) - You work with multiple languages (Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, Dockerfile) ## How It Works ### Three-Phase Architecture Every time OpenAI Codex edits or writes a file, Plankton's `multi_linter.sh` PostToolUse hook runs: ``` Phase 1: Auto-Format (Silent) ├─ Runs formatters (ruff format, biome, shfmt, taplo, markdownlint) ├─ Fixes 40-50% of issues silently └─ No output to main agent Phase 2: Collect Violations (JSON) ├─ Runs linters and collects unfixable violations ├─ Returns structured JSON: {line, column, code, message, linter} └─ Still no output to main agent Phase 3
- When to Use
- How It Works
- Three-Phase Architecture
- What the Main Agent Sees
- Config Protection (Defense Against Rule-Gaming)
- Package Manager Enforcement
- Setup
- Quick Start
- Per-Project Integration
- Language-Specific Dependencies
- Pairing with ecc
- Complementary, Not Overlapping
- Recommended Combination
- Avoiding Hook Conflicts
Install core dependencies brew install jaq ruff uv Install Python linters uv sync --all-extras Start OpenAI Codex — hooks activate automatically codex export ecc_HOOK_PROFILE=strict export ecc_QUALITY_GATE_FIX=true export ecc_QUALITY_GATE_STRICT=true
What does the plankton-code-quality skill do?
Write-time code quality enforcement using Plankton — auto-formatting, linting, and Codex-powered fixes on every file edit via hooks.
How do I install it?
Run `npx skills add mturac/everything-openai-codex --skill plankton-code-quality --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mturac/everything-openai-codex, a repository with 84 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.