plankton-code-quality

Enforce linting and formatting on every file edit via Claude Code hooks.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/luongldptit/move-ticket --skill plankton-code-quality-luongldptit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plankton-code-quality
Source: https://github.com/luongldptit/move-ticket/tree/main/.agent/skills/plankton-code-quality
Command: npx skills add https://github.com/luongldptit/move-ticket --skill plankton-code-quality-luongldptit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the hassle of manual code quality checks and catches formatting, linting, and logic issues the moment you edit a file, instead of waiting until commit time. It also prevents AI agents from tampering with linter configurations to bypass quality rules.

Core Features & Use Cases

  • Write-time quality enforcement: Runs formatters and linters automatically on every file edit via Claude Code hooks, fixing 40-50% of issues silently without interrupting your workflow.
  • AI-powered violation fixes: Spawns Claude subprocesses to resolve complex linting issues, routing to the appropriate model tier (Haiku for style, Sonnet for logic, Opus for types) based on issue complexity.
  • Config tamper protection: Blocks edits to linter configuration files to stop agents from disabling rules instead of fixing code, with pre-edit blocking and post-session detection. Use case: For example, if you're working on a multi-language codebase with Python, TypeScript, and Shell scripts, this Skill automatically formats all files, catches linting errors, and fixes them without you needing to run manual checks or worry about agents breaking quality rules.

Quick Start

Use the plankton-code-quality skill to automatically enforce formatting and linting rules on all code files you edit in your current project.

Frequently Asked Questions about plankton-code-quality

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I auto-format code and run linters automatically on every file edit?

Auto-formatting on every file edit is achieved by running formatters and linters via Claude Code write-time hooks, fixing 40-50% of issues silently without interrupting your workflow.

How do I prevent AI agents from bypassing linting rules or modifying configuration files?

To prevent AI agents from bypassing linting rules, you need linter config tamper protection that blocks edits to configuration files with pre-edit blocking and post-session detection.

Can I enforce code quality checks across Python, TypeScript, and Shell scripts simultaneously?

Yes, you can enforce code quality checks across multi-language codebases including Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, and Dockerfile file types.

How do I automatically fix complex linting violations using AI?

Automated AI-powered violation fixes spawn Claude subprocesses to resolve complex linting issues, routing to Haiku for style, Sonnet for logic, and Opus for types.

What is write-time code quality enforcement and how does it differ from commit-time checks?

Write-time code quality enforcement runs formatters and linters the moment you edit a file, catching issues immediately instead of delaying feedback until commit time.

Does this approach work for blocking legacy package managers in software development workflows?

Yes, write-time enforcement hooks satisfy requirements for legacy package manager blocking alongside auto-formatting and lint violation remediation across Claude Code workflows.