code-reviewer
Perform code review with DDD architecture compliance check. Triggers: review, ็จๅผ็ขผๅฏฉๆฅ, code review, ๅฏฉๆฅ, CR.
Perform code review with DDD architecture compliance check. Triggers: review, ็จๅผ็ขผๅฏฉๆฅ, code review, ๅฏฉๆฅ, CR.
่คๆฐใฎAIใฌใใฅใขใผ๏ผCodexใCodeRabbitใCopilotใGemini๏ผใไธฆๅๅฎ่กใใ็ตๆใ็ตฑๅๅฆ็ใใฆๅไธใฎใฌใใผใใ็ๆใใพใใ้่คๆ้คใๅชๅ ๅบฆไปใใใซใใดใชๅ้กใ่ชๅๅใใพใใๅ ๆฌ็ใชใณใผใใฌใใฅใผใๅค่ง็ใช่ฆ็นใงใฎๅ่ณช่ฉไพกใ่คๆฐAIใฎๅผทใฟใๆดปใใใใฌใใฅใผใๅฟ ่ฆใชๅ ดๅใซไฝฟ็จใใฆใใ ใใใ
Security-focused code review guidelines for identifying vulnerabilities
Critical code review methodology. Use when reviewing code, PRs, or changes to enforce rigorous review standards.
Code review skill that checks TypeScript type safety, exported for use by cross-cutting review plugin
Use when creating a new ESLint rule for eslint-cease-nonsense-rules, adding a lint rule, or when user provides incorrect/correct code examples for a new rule
์ฝ๋ ํ์ง์ ๊ฒํ ํฉ๋๋ค. "์ฝ๋ ๋ฆฌ๋ทฐ", "review", "๊ฒํ " ์์ฒญ ์ ์ฌ์ฉํฉ๋๋ค.
Write consistent, maintainable CSS following the project's methodology (Tailwind, BEM, utility classes, CSS modules) with design system adherence and performance optimization. Use this skill when writing or modifying styles, CSS files, utility classes, CSS-in-JS, styled components, or any styling code. Apply when working with .css, .scss, .module.css files, Tailwind utility classes, styled-components, CSS modules, design tokens (colors, spacing, typography), framework-specific styling approaches, optimizing CSS for production, implementing CSS purging or tree-shaking, or avoiding style overrides. Use for any task involving visual styling, layout styling, design system implementation, or CSS organization.
.NET ์ฝ๋์์ ์ ์ ๋ถ์(Static analysis), ๋ณด์ ์ค์บ(Security scan) ๋ฐ ์ข ์์ฑ ์ฒดํฌ(Dependency check)๋ฅผ ์ํํฉ๋๋ค. ์ฝ๋ ํ์ง, ๋ณด์ ๊ฐ์ฌ ๋๋ ์ทจ์ฝ์ ํ์ง๊ฐ ํฌํจ๋ ์์ ์์ ์ฌ์ฉํฉ๋๋ค.
Handle code review feedback with technical rigor, verification, and appropriate pushback. WHEN: MUST use when received code review feedback. Invoke with "/receiving-code-review" or "handle this review feedback", "respond to review". WHEN NOT: Requesting code review (use requesting-code-review), writing code, debugging.
Review test quality before PR - semantic analysis of test design, not just linting
Perform pre-flight checks for required info, project state, and missing context. Use before starting work to avoid gaps.
Executes the Python Refactoring Loop to improve code quality without changing behavior. Iterates through analysis, improvement, and verification using `python-verification` until all standards (SSOT, Ruff, Mypy) are met.
Generates custom design system rules for your codebase
Ruby 3.4+ best practices with RSpec 4, RuboCop 2, Bundler, and Rails 8 patterns.
Ensure code quality before commits. Run lint, format, test, build. Use npm scripts: npm run lint, npm run format, npm test, npm run build. CRITICAL: All tests must pass, no lint errors, code must be formatted before committing.
Enforces universal strict governance rules (500 lines, 5 funcs, 4 args) and interface-first I/O for Python, Golang, and .NET.
Enforces Zig coding conventions from the Zig Zero to Hero guide. Use when writing, reviewing, or refactoring Zig code. Applies naming conventions, error handling patterns, resource management, and module organization best practices.
ๆง่กไปฃ็ ่ดจ้้จ็ฆๆฃๆฅ๏ผๆต่ฏ้่ฟโ่ฆ็็โLintโGOAL่ฟฝๆบฏโๅฏๆไบค๏ผ๏ผ้ช่ฏๅๅ ๆต่ฏ่ฆ็็โฅ80%ใ้ๆๆต่ฏ้่ฟ็โฅ95%ใไปฃ็ ่ง่้ถ้่ฏฏใๅฝๅฎๆไปฃ็ ๅฎ็ฐใๅๅคๆไบคไปฃ็ ใ้่ฆ่ดจ้้ช่ฏใ่ฟ่กๆไบคๅ่ชๆฃๆถไฝฟ็จใ็กฎไฟไปฃ็ ๅฏๅๅนถใ
Validate translation keys exist in both Polish and English locale files before committing. Use when adding new user-facing text or translation keys.
ใณใผใๅ่ณชๅบๆบใฎๅฎๅ จ้ตๅฎใไฟ่จผใใพใใใณใใใๅใฎๅ่ณชใใงใใฏใ่ชๅๅฎ่กใใใจใฉใผใใใ็ถๆ ใงใฎใณใใใใ้ฒๆญขใใพใใ
JavaScript/TypeScript stack configuration - pnpm, prettier, eslint, vitest with 96% coverage threshold
Analyze the codebase for security vulnerabilities, including dependency issues, improper data handling, and configuration risks.
Ensures Zod v4 patterns are used correctly throughout the codebase. Apply when creating or modifying validation schemas, form schemas, or any Zod validators. Enforces v4 syntax and prevents deprecated v3 patterns.