plankton-code-quality

Enforce code quality via automated linting and formatting hooks.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/ThejanaJayalath/Niolla-PM-system --skill plankton-code-quality-thejanajayalath
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plankton-code-quality
Source: https://github.com/ThejanaJayalath/Niolla-PM-system/tree/main/.cursor/skills/plankton-code-quality
Command: npx skills add https://github.com/ThejanaJayalath/Niolla-PM-system --skill plankton-code-quality-thejanajayalath

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jaq, ruff, uv, biome, shellcheck, shfmt, yamllint, markdownlint-cli2, hadolint, taplo.

What problem does it solve?

This skill prevents code quality degradation by enforcing strict linting and formatting rules during the write-time process, rather than waiting for commit-time checks.

Core Features & Use Cases

  • Automated Remediation: Automatically runs formatters and linters on every file edit, with Claude-powered subprocesses to fix violations the agent misses.
  • Config Protection: Blocks unauthorized modifications to linter configuration files to ensure consistent enforcement.
  • Tiered Model Routing: Dynamically routes fix requests to different AI models based on the complexity of the code violation.

Quick Start

Activate the plankton code quality skill to begin monitoring and automatically fixing linting violations in your current project directory.

Frequently Asked Questions about plankton-code-quality

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

FAQPage Schema
How do I enforce real-time linting and formatting during code generation?

Automated code quality enforcement uses PostToolUse hooks to intercept file edits, automatically running configured linters and formatters to resolve violations immediately during the write-time process.

Do I need to install linters locally to automate code quality remediation?

Yes, local installation of language-specific linters and formatters like ruff, biome, and shellcheck is required to maintain strict adherence to project configuration standards during automated remediation.

What's the best way to prevent unauthorized modifications to linter configuration files?

Config protection blocks unauthorized modifications to linter configuration files, ensuring consistent enforcement of formatting and linting rules across the project without manual oversight.

Can I route automated code fixes to different AI models based on violation complexity?

Tiered model routing dynamically routes fix requests to different AI models based on the complexity of the code violation, optimizing Claude-powered subprocesses to fix violations the agent misses.

How does write-time code quality enforcement compare to commit-time checks?

Write-time enforcement prevents code quality degradation by running automated linting and formatting on every file edit, rather than waiting for commit-time checks to identify violations after the fact.