
Plankton Code Quality
- 5.2k installs
- 234k repo stars
- Updated July 27, 2026
- affaan-m/everything-claude-code
plankton-code-quality integrates Plankton write-time code quality enforcement with auto-formatting, linting, and Claude-powered fixes on every file edit via hooks.
About
The plankton-code-quality skill documents Plankton, a write-time code quality enforcement system for Claude Code credited to @alxfazio. On every file edit, the multi_linter.sh PostToolUse hook runs three phases: silent auto-format with ruff format, biome, shfmt, taplo, and markdownlint fixing roughly forty to fifty percent of issues; JSON violation collection with line, column, code, message, and linter fields; then a claude -p subprocess that routes fixes to Haiku, Sonnet, or Opus by violation complexity with verify reruns. The main agent sees nothing when clean or fixed, or hook violation counts when fixes remain. Config protection uses PreToolUse blocks on linter configs, a stop hook git diff guardian, and protects .ruff.toml, biome.json, and related files. Bash PreToolUse blocks legacy pip and npm package managers favoring uv and bun. Setup requires manual install with brew install jaq ruff uv, uv sync --all-extras, and copying .claude hooks plus settings.json for per-project use across Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, and Dockerfile.
- PostToolUse multi_linter.sh runs format, lint, and Claude subprocess fixes.
- Tiered Haiku, Sonnet, and Opus routing by violation complexity codes.
- PreToolUse blocks edits to linter config files against rule gaming.
- Bash hook blocks pip and npm in favor of uv and bun.
- Supports Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, Dockerfile.
Plankton Code Quality by the numbers
- 5,219 all-time installs (skills.sh)
- +274 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #36 of 1,382 Code Review & Quality skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
plankton-code-quality capabilities & compatibility
- Capabilities
- three phase posttooluse format lint and delegate · structured json violation collection per linter · tiered claude p subprocess fix routing with tim · pretooluse and stop hook linter config protectio · package manager enforcement favoring uv and bun
- Works with
- github
- Use cases
- code review · testing · refactoring
- Platforms
- macOS · Linux
- Runs
- Runs locally
- Pricing
- Free
What plankton-code-quality says it does
Write-time code quality enforcement using Plankton — auto-formatting, linting, and Claude-powered fixes on every file edit via hooks.
Fixes 40-50% of issues silently
LLMs will modify `.ruff.toml` or `biome.json` to disable rules rather than fix code.
npx skills add https://github.com/affaan-m/everything-claude-code --skill plankton-code-qualityAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 5.2k |
|---|---|
| repo stars | ★ 234k |
| Security audit | 0 / 3 scanners passed |
| Last updated | July 27, 2026 |
| Repository | affaan-m/everything-claude-code ↗ |
How do I keep agent-written code formatted and lint-clean on every edit instead of only at commit time, while stopping config rule gaming?
Enforce write-time formatting and linting on every Claude Code file edit with hook-driven auto-fixes and config protection.
Who is it for?
Claude Code projects wanting per-edit format and lint enforcement across Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, and Dockerfile.
Skip if: Repos without Claude Code hooks or teams that only want pre-commit checks without write-time enforcement.
When should I use this skill?
User wants automatic formatting and linting on every file edit, tiered model fix routing, or defense against agents disabling linter rules.
What you get
Most violations fixed silently; remaining issues reported as hook counts after subprocess verification reruns.
- PostToolUse hook configuration
- Auto-fixed source files
By the numbers
- Phase 1 auto-format fixes 40-50% of issues silently
- Haiku fix timeout 120s, Sonnet 300s, Opus 600s
- Supports eight language families including Python and TypeScript
Files
plankton-code-quality - 日本語翻訳進行中
このファイルの翻訳は実装中です。英語版は元のスキルファイルを参照してください。
詳細は:D:/tmp/everything-claude-code/skills/plankton-code-quality/SKILL.md
Related skills
Forks & variants (1)
Plankton Code Quality has 1 known copy in the catalog totaling 1.3k installs. They canonicalize to this original listing.
- affaan-m - 1.3k installs
How it compares
Use plankton-code-quality for per-edit hook enforcement; use pre-commit-only linters when write-time automation is unnecessary.
FAQ
What does the main Claude Code agent see from Plankton?
Nothing when there are no violations or the subprocess fixes them; otherwise a hook message with the remaining violation count and exit code 2.
How does Plankton stop agents from weakening linter configs?
PreToolUse protect_linter_configs.sh blocks config edits, stop_config_guardian.sh checks git diff at session end, and a protected files list covers .ruff.toml, biome.json, and related configs.
How do I add Plankton to an existing project?
Copy the .claude/hooks directory, .claude/settings.json hook configuration, linter config files, and install the linters for your languages.
Is Plankton Code Quality safe to install?
skills.sh reports 0 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.