plankton-code-quality
ไฝฟ็จPlankton่ฟ่ก็ผๅๆถไปฃ็ ่ดจ้ๅผบๅถๆง่กโโ้่ฟ้ฉๅญๅจๆฏๆฌกๆไปถ็ผ่พๆถ่ชๅจๆ ผๅผๅใไปฃ็ ๆฃๆฅๅClaude้ฉฑๅจ็ไฟฎๅคใ
ไฝฟ็จPlankton่ฟ่ก็ผๅๆถไปฃ็ ่ดจ้ๅผบๅถๆง่กโโ้่ฟ้ฉๅญๅจๆฏๆฌกๆไปถ็ผ่พๆถ่ชๅจๆ ผๅผๅใไปฃ็ ๆฃๆฅๅClaude้ฉฑๅจ็ไฟฎๅคใ
Pythonic ๆฏ็จๆณใPEP 8 ๆ ๅใ็ฑปๅๆ็คบไปฅๅๆๅปบ็จณๅฅใ้ซๆไธๅฏ็ปดๆค็ Python ๅบ็จ็จๅบ็ๆไฝณๅฎ่ทตใ
ไธบๅ็็ฎกๅถ้ ไธไธญ็่ดจ้ๆงๅถใไธๅๆ ผ่ฐๆฅใๆ นๆฌๅๅ ๅๆใ็บ ๆญฃๆชๆฝๅไพๅบๅ่ดจ้็ฎก็ๆไพ็ผ็ ๅไธไธ็ฅ่ฏใๅบไบๅจFDAใIATF 16949ๅAS9100็ฏๅขไธญๆฅๆ15ๅนดไปฅไธ็ป้ช็่ดจ้ๅทฅ็จๅธ็่ง่งฃใๅ ๆฌไธๅๆ ผๆฅๅ็ๅฝๅจๆ็ฎก็ใ็บ ๆญฃไธ้ข้ฒๆชๆฝ็ณป็ปใ็ป่ฎก่ฟ็จๆงๅถ่งฃ้ๅๅฎกๆ ธๆนๆณใ้็จไบ่ฐๆฅไธๅๆ ผใ่ฟ่กๆ นๆฌๅๅ ๅๆใ็ฎก็็บ ๆญฃไธ้ข้ฒๆชๆฝใ่งฃ้็ป่ฎก่ฟ็จๆงๅถๆฐๆฎๆๅค็ไพๅบๅ่ดจ้้ฎ้ขใlicense: Apache-2.0
Claude Code ไผ่ฏ็ๅ จ้ข้ช่ฏ็ณป็ปใ
A comprehensive verification system for Kiro sessions.
Interactive installer for Everything Claude Code โ guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.
C++ coding standards based on the C++ Core Guidelines (isocpp.github.io). Use when writing, reviewing, or refactoring C++ code to enforce modern, safe, and idiomatic practices.
Formal evaluation framework for Claude Code sessions implementing eval-driven development (EDD) principles
Write-time code quality enforcement using Plankton โ auto-formatting, linting, and Claude-powered fixes on every file edit via hooks.
Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.
A comprehensive verification system for Claude Code sessions.
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Use when you have a spec or requirements for a multi-step task, before touching code
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when implementing any feature or bugfix, before writing implementation code
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.
Refactor high-complexity React components in Dify frontend. Use when `pnpm analyze-component --json` shows complexity > 50 or lineCount > 300, when the user asks for code splitting, hook extraction, or complexity reduction, or when `pnpm analyze-component` warns to refactor before testing; avoid for simple/well-structured components, third-party wrappers, or when the user explicitly wants testing without refactoring.
Trigger when the user requests a review of frontend files (e.g., `.tsx`, `.ts`, `.js`). Support both pending-change reviews and focused file reviews while applying the checklist rules.
Refactor high-complexity React components in Dify frontend. Use when `pnpm analyze-component --json` shows complexity > 50 or lineCount > 300, when the user asks for code splitting, hook extraction, or complexity reduction, or when `pnpm analyze-component` warns to refactor before testing; avoid for simple/well-structured components, third-party wrappers, or when the user explicitly wants testing without refactoring.
Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string updates and prompt adjustments for known Opus 4.5 behavioral differences. Does NOT migrate Haiku 4.5.
Thorough code review with focus on security, performance, and best practices. Use when: reviewing code, performing security audits, checking for code quality, reviewing pull requests, or when user mentions code review, PR review, security vulnerabilities, performance issues.
Use this skill when asked to review text and user-facing strings within the codebase. It ensures that these strings follow rules on clarity, usefulness, brevity and style.
Migrate a file to use stricter Pyrefly type checking with annotations required for all functions, classes, and attributes.