code-quality
150.4K
plankton-code-quality
使用Plankton进行编写时代码质量强制执行——通过钩子在每次文件编辑时自动格式化、代码检查和Claude驱动的修复。
affaan-m
testing-security
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
code-quality
150.4K
python-patterns
Pythonic 惯用法、PEP 8 标准、类型提示以及构建稳健、高效且可维护的 Python 应用程序的最佳实践。
affaan-m
testing-security
code-quality
150.4K
quality-nonconformance
为受监管制造业中的质量控制、不合格调查、根本原因分析、纠正措施和供应商质量管理提供编码化专业知识。基于在FDA、IATF 16949和AS9100环境中拥有15年以上经验的质量工程师的见解。包括不合格报告生命周期管理、纠正与预防措施系统、统计过程控制解释和审核方法。适用于调查不合格、进行根本原因分析、管理纠正与预防措施、解释统计过程控制数据或处理供应商质量问题。license: Apache-2.0
affaan-m
testing-security
code-quality
150.4K
verification-loop
A comprehensive verification system for Kiro sessions.
affaan-m
testing-security
code-quality
150.4K
configure-ecc
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.
affaan-m
testing-security
code-quality
150.4K
cpp-coding-standards
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.
affaan-m
testing-security
code-quality
150.4K
eval-harness
Formal evaluation framework for Claude Code sessions implementing eval-driven development (EDD) principles
affaan-m
testing-security
code-quality
150.4K
plankton-code-quality
Write-time code quality enforcement using Plankton — auto-formatting, linting, and Claude-powered fixes on every file edit via hooks.
affaan-m
testing-security
code-quality
150.4K
springboot-verification
Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.
affaan-m
testing-security
code-quality
150.4K
verification-loop
A comprehensive verification system for Claude Code sessions.
affaan-m
testing-security
code-quality
145.9K
verification-before-completion
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
obra
testing-security
code-quality
145.9K
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
obra
testing-security
code-quality
145.9K
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
obra
testing-security
code-quality
145.9K
receiving-code-review
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
obra
testing-security
code-quality
145.9K
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
obra
testing-security
code-quality
137.2K
backend-code-review
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.
langgenius
testing-security
code-quality
137.2K
component-refactoring
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.
langgenius
testing-security
code-quality
126.5K
frontend-code-review
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.
langgenius
testing-security
code-quality
126.5K
component-refactoring
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.
langgenius
testing-security
code-quality
112.2K
claude-opus-4-5-migration
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.
anthropics
testing-security
code-quality
105.1K
code-reviewer
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.
Shubhamsaboo
testing-security
code-quality
100.9K
string-reviewer
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.
google-gemini
testing-security
code-quality
99K
pyrefly-type-coverage
Migrate a file to use stricter Pyrefly type checking with annotations required for all functions, classes, and attributes.
pytorch
testing-security