What problem does it solve?
This Skill eliminates the risk of inconsistent code quality, missed linting errors, and agents bypassing quality rules by modifying linter configurations instead of fixing actual code, which occurs when quality checks only run at commit time rather than during writing.
Core Features & Use Cases
- Write-time quality enforcement: Runs formatters and linters automatically on every file edit via Claude Code hooks, catching style, lint, and type issues before they accumulate in the codebase.
- Tiered AI-powered violation fixes: Spawns Claude subprocesses to resolve unfixed violations, routing simple style issues to Haiku, complex refactoring to Sonnet, and deep type system problems to Opus for efficient, cost-effective remediation.
- Config tamper protection: Blocks edits to linter configuration files and detects post-hoc changes to prevent agents from disabling rules to pass checks instead of fixing code.
Use case: For solo developers and engineering teams using Claude Code, this ensures all code adheres to project standards without manual pre-commit checks, and prevents rule-gaming that would let low-quality, non-compliant code slip through code review.
Quick Start
Use the plankton-code-quality skill to automatically enforce code formatting and linting rules on every file you edit in Claude Code, with AI-powered fixes for any violations that formatters cannot resolve.
