home/categories/code-quality
category focus

Code Quality

Linters, formatters, and static analysis.

2681টি স্কিলall categories
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
code-quality
1

review-standard

Systematic code review skill checking documentation quality and promoting code reuse

MAdrid1011
MAdrid1011
testing-security
open
code-quality
1

podcast-feed-validator

Validate podcast RSS feed against specification standards. Checks channel metadata, episode elements, XML structure, and file metadata accuracy. Use after updating feed.xml with a new episode to ensure compliance with RSS spec. References docs/RSS-specification.md for requirements.

yudame
yudame
testing-security
open
code-quality
1

check-i18n

This skill validates i18n (internationalization) key consistency across Go source and TOML locale files. Use when adding, modifying, or reviewing i18n keys in this project to ensure `internal/i18n/keys.go` stays in sync with `internal/i18n/locales/*.toml` files.

xzzpig
xzzpig
testing-security
open
code-quality
1

pre-fix-eval

修復前強制評估系統. Use for: (1) 測試失敗自動評估, (2) 編譯錯誤分類處理, (3) 強制 Ticket 開設流程

tarrragon
tarrragon
testing-security
open
code-quality
1

code-review-standards

Comprehensive code review standards covering security, quality, performance, testing, and documentation. Includes checklists, common issues, and best practices for thorough code reviews.

squirrelsoft-dev
squirrelsoft-dev
testing-security
open
code-quality
1

elixir-ash-reviewer

Comprehensive code review system for Elixir applications using Phoenix, LiveView, Ash Framework, LiveSvelte, TailwindCSS, and DaisyUI. Performs deep analysis of code quality, architectural patterns, test coverage, and Ash-specific best practices. Use when (1) Reviewing Elixir/Phoenix/Ash codebases for quality and best practices, (2) Analyzing test suite quality and brittleness, (3) Ensuring Ash framework patterns are properly implemented, (4) Identifying architectural improvements, (5) Reviewing LiveView/LiveSvelte component structure, (6) Validating resource design and API patterns

Oxmus
Oxmus
testing-security
open
code-quality
1

stable-version

各言語/フレームワークの安定版バージョン確認ガイド。 LTSの考え方、EOLチェック、アップグレード判断をサポート。

sk8metalme
sk8metalme
testing-security
open
code-quality
1

golang-review

Go code standards enforcing idiomatic patterns, safety, and maintainability. Use when writing, generating, or reviewing Go code.

javiertelioz
javiertelioz
testing-security
open
code-quality
1

whole-reviewer

Post-editing validation for Whole documentation. Use when: (1) After completing edits, (2) Before marking task complete, (3) Validating cross-reference updates, (4) Verifying bilingual consistency, (5) Final quality check.

Goobee811
Goobee811
testing-security
open
code-quality
1

flutter-review-receive

Use when receiving code review feedback - requires technical evaluation and verification, not performative agreement or blind implementation

vp-k
vp-k
testing-security
open
code-quality
1

comprehensive-tracing

Enforces thorough code analysis with all entry points, complete flow tracing, architectural reasoning, and consumption tracking

krwhynot
krwhynot
testing-security
open
code-quality
1

tm-definition-of-done

Enforce Tavern Master definition of done (lint + tests + formatting + plan updates).

JonWhiteFang
JonWhiteFang
testing-security
open
code-quality
1

code-review

Guidelines for reviewing and improving code quality in YT Lite v3.

Raw1mage
Raw1mage
testing-security
open
code-quality
1

python-pep8-style

Use this skill when writing Python code following PEP 8 and modern Python best practices. Provides comprehensive guidance on code layout, naming conventions, EAFP philosophy, type hints, exception handling, and pytest-based TDD. Covers all critical PEP 8 rules including indentation, imports, whitespace, documentation, and idiomatic Python patterns. Appropriate for any task involving .py files, Python code reviews, refactoring, or ensuring Python code quality.

nhlongnguyen
nhlongnguyen
testing-security
open
code-quality
1

sorry-checker

Check that no sorry placeholders exist in the codebase. Use after making changes or when asked to verify proof completeness.

Arthur742Ramos
Arthur742Ramos
testing-security
open
code-quality
1

config-validator

Validates KrakenD configurations with specific error fixes, edition compatibility checks, anti-pattern detection, and Flexible Configuration support

krakend
krakend
testing-security
open
code-quality
1

codeql-expert

Expert-level CodeQL for static analysis, vulnerability detection, and security code scanning

personamanagmentlayer
personamanagmentlayer
testing-security
open
code-quality
1

check-team-codex

Validate code against Team Codex standards. Use when (1) before creating commits, (2) during verification phase, (3) quality gate enforcement.

semicolon-devteam
semicolon-devteam
testing-security
open
code-quality
1

fmt

Format TypeScript sources using Deno formatter

sachitv
sachitv
testing-security
open
code-quality
1

code-review

Reviews code for quality, security, and maintainability. Use after implementing features, completing significant work, or when user asks for code review.

jcdoll
jcdoll
testing-security
open
code-quality
1

code-quality-checker

코드 품질 검사 자동화. 린트, 포맷, 타입 체크, 보안 스캔 통합.

garimto81
garimto81
testing-security
open
code-quality
1

vue

Vue coding style and best practices.

rakibdev
rakibdev
testing-security
open
code-quality
1

tech-article-review

技術記事の推敲と品質向上を支援するskill。記事を読み、構造・読みやすさ・技術的正確性・表現の明確さ・コードサンプルの品質をチェックし、改善提案を行う。ユーザーが「記事を推敲して」「記事をレビューして」「記事の品質をチェックして」などと依頼した際に使用する。

yahsan2
yahsan2
testing-security
open
Previous
Page 81 / 112
Next