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.
修復前強制評估系統. Use for: (1) 測試失敗自動評估, (2) 編譯錯誤分類處理, (3) 強制 Ticket 開設流程
Comprehensive code review standards covering security, quality, performance, testing, and documentation. Includes checklists, common issues, and best practices for thorough code reviews.
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
各言語/フレームワークの安定版バージョン確認ガイド。 LTSの考え方、EOLチェック、アップグレード判断をサポート。
Go code standards enforcing idiomatic patterns, safety, and maintainability. Use when writing, generating, or reviewing Go code.
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.
Use when receiving code review feedback - requires technical evaluation and verification, not performative agreement or blind implementation
Enforces thorough code analysis with all entry points, complete flow tracing, architectural reasoning, and consumption tracking
Enforce Tavern Master definition of done (lint + tests + formatting + plan updates).
Guidelines for reviewing and improving code quality in YT Lite v3.
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.
Check that no sorry placeholders exist in the codebase. Use after making changes or when asked to verify proof completeness.
Validates KrakenD configurations with specific error fixes, edition compatibility checks, anti-pattern detection, and Flexible Configuration support
Expert-level CodeQL for static analysis, vulnerability detection, and security code scanning
Validate code against Team Codex standards. Use when (1) before creating commits, (2) during verification phase, (3) quality gate enforcement.
Reviews code for quality, security, and maintainability. Use after implementing features, completing significant work, or when user asks for code review.
코드 품질 검사 자동화. 린트, 포맷, 타입 체크, 보안 스캔 통합.
技術記事の推敲と品質向上を支援するskill。記事を読み、構造・読みやすさ・技術的正確性・表現の明確さ・コードサンプルの品質をチェックし、改善提案を行う。ユーザーが「記事を推敲して」「記事をレビューして」「記事の品質をチェックして」などと依頼した際に使用する。
Configures modern TypeScript (4.9+ through 5.x) for maximum type safety with sustainable compile times. Use when designing type-safe configs/maps/APIs, enforcing strictness flags, improving TS build performance (incremental, project references), or setting up separate TS/ESLint configs for tests.
Maintain Python code quality using Black formatting, Ruff linting, and mypy type checking. Use when formatting code, running linters, fixing style issues, or adding type hints.
