Plankton Write-Time Code Quality
Enforce code quality on every file edit: silent auto-formatting, 20+ linters, Claude-powered fixes with tiered model routing, plus config tamper protection.
- What
- Enforce code quality on every file edit: silent auto-formatting, 20+ linters, Claude-powered fixes with tiered model routing, plus config tamper protection.
- Cost
- Free
- Needs
- Use "Plankton Write-Time Code Quality" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: an integration reference for Plankton (by @alxfazio), a write-time code quality enforcement system for Claude Code. Every file edit triggers a three-phase PostToolUse hook: silent auto-formatting (ruff format, biome, shfmt and friends fix 40 to 50 percent of issues invisibly), violation collection as structured JSON, then delegation to a claude subprocess that fixes what the agent missed, routing by complexity (Haiku for style, Sonnet for complexity and refactoring, Opus for deep type reasoning) and re-verifying afterward. The main agent only ever sees violations the subprocess could not fix. Plankton also defends against rule-gaming: a PreToolUse hook blocks edits to linter configs, a stop hook catches config changes at session end, and a Bash hook blocks legacy package managers in favor of uv and bun. Setup is manual (install the linters, copy the hooks and configs into your project), it covers Python, TypeScript, Shell, YAML, JSON, TOML, Markdown and Dockerfiles, and it pairs with ECC rather than replacing it. A community contribution to the ECC collection. By @affaan-m, listed here with credit to its creator, Plankton itself by @alxfazio. From the affaan-m/ECC repository (MIT). Honest caveats: installation is manual, review the hook code before installing it; spawning model subprocesses on every edit costs tokens and time, so tune the language gates and timeouts for your project. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Plankton Write-Time Code Quality" with your Muse. Prerequisites: manual installation. Install the linters for your languages (ruff, biome, shellcheck, etc.), copy the Plankton hooks and configs into your project, review the hook code first. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/plankton-code-quality/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Set up Plankton write-time quality enforcement in this project for these languages: [list them]." 3. Tune the config: disable languages you do not use, set timeouts, and resolve any hook conflicts with ECC's own Prettier hook. Tip: start with subprocess delegation on, then disable it (HOOK_SKIP_SUBPROCESS=1) if edits feel too slow. Safety: a skill is plain-text instructions; it runs nothing by itself. Review the hook code before installing it; hooks run shell commands on every file edit. Review generated commands before running them.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.