
Plankton Code Quality
- 1.4k installs
- 238k repo stars
- Updated August 5, 2026
- affaan-m/ecc
This is a copy of plankton-code-quality by affaan-m - installs and ranking accrue to the original listing.
plankton-code-quality is a Claude Code skill that applies automatic formatting, linting, and Claude-powered fixes on every file edit without waiting for commit time.
About
plankton-code-quality is an ECC-origin skill that keeps code clean during active editing rather than deferring quality checks to pre-commit hooks or CI. It triggers formatting, lint passes, and Claude-assisted fixes immediately after file changes so developers see corrected code before pushing. Teams reach for plankton-code-quality when noisy lint debt accumulates between commits or when they want agent-driven fix suggestions inline with edits. The skill fits projects with established formatters and linters wired into the workspace. It complements but does not replace full test suites or security review pipelines.
- Runs on every file edit via PostToolUse hooks instead of only at commit
- Three-phase architecture: silent auto-format, violation collection, then tiered model routing for fixes
- Defense against agents modifying linter configs to pass instead of fixing code
- Supports Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, Dockerfile
- Tiered model routing: Haiku for simple style, Sonnet for logic, Opus for types
Plankton Code Quality by the numbers
- 1,359 all-time installs (skills.sh)
- +83 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/affaan-m/ecc --skill plankton-code-qualityAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.4k |
|---|---|
| repo stars | ★ 238k |
| Last updated | August 5, 2026 |
| Repository | affaan-m/ecc ↗ |
How do you fix lint errors on every file edit?
Get automatic formatting, linting, and Claude-powered fixes on every file edit without waiting for commit time.
Who is it for?
Developers who want continuous formatter and linter enforcement during editing rather than only at commit or CI time.
Skip if: Teams relying solely on CI for quality, projects without configured linters, or workflows needing formal security audit gates.
When should I use this skill?
User wants automatic formatting, lint fixes, or Claude-powered code quality corrections applied on each file save or edit.
What you get
Formatted source files with lint violations resolved and Claude-suggested fixes applied inline.
- Formatted files
- Lint-cleaned source
Files
plankton-code-quality - 日本語翻訳進行中
このファイルの翻訳は実装中です。英語版は元のスキルファイルを参照してください。
詳細は:D:/tmp/everything-claude-code/skills/plankton-code-quality/SKILL.md
Related skills
How it compares
Pick plankton-code-quality over generic lint skills when the goal is edit-time auto-fix loops inside an ECC workspace.
FAQ
When does plankton-code-quality run checks?
plankton-code-quality runs formatting, linting, and Claude-powered fixes on every file edit during development, rather than waiting for a git commit or CI pipeline.
Does plankton-code-quality replace pre-commit hooks?
plankton-code-quality complements pre-commit hooks by catching issues earlier at edit time. Teams may still keep hooks or CI for tests and security gates.