review-standard
Systematic code review skill checking documentation quality and promoting code reuse
Systematic code review skill checking documentation quality and promoting code reuse
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.
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ใ่จไบใ่ชญใฟใๆง้ ใป่ชญใฟใใใใปๆ่ก็ๆญฃ็ขบๆงใป่กจ็พใฎๆ็ขบใใปใณใผใใตใณใใซใฎๅ่ณชใใใงใใฏใใๆนๅๆๆกใ่กใใใฆใผใถใผใใ่จไบใๆจๆฒใใฆใใ่จไบใใฌใใฅใผใใฆใใ่จไบใฎๅ่ณชใใใงใใฏใใฆใใชใฉใจไพ้ ผใใ้ใซไฝฟ็จใใใ