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.