Systematic code review using quality gates, SOLID principles, error handling patterns, and test coverage analysis. Provides structured feedback with severity levels and actionable improvements.
Validate UE5 Python scripts for correctness, check for deprecated APIs, and verify parameter constraints.
Comprehensive TypeScript best practices including type imports, security patterns, code structure, and early returns. Use when writing TypeScript code, reviewing for quality, implementing error handling, or ensuring type safety.
Brutally honest code review in the style of Linus Torvalds, focusing on data structures, simplicity, and pragmatism. Use when you want critical, no-nonsense feedback that prioritizes engineering fundamentals over style preferences.
Apply kinemotion development standards. Use when writing Python code, creating tests, modifying the kinemotion codebase, or reviewing code quality.
Use when setting up code quality enforcement - configures linting, formatting, pre-commit hooks, CI workflows, and review checklists with advisory/soft/hard enforcement levels
Use when comments are growing faster than clarity: many “what” comments, frequent drift, or code that needs explanation to be understood. Goal: encode intent in names and structure, and keep only high-value text such as contracts, why, and gotchas.
Xcodeプロジェクトのビルド設定を検証・修正するスキル。推奨設定との比較、問題の検出、修正提案を行う。使用シーン：(1)「ビルド設定を確認して」「プロジェクト設定をチェックして」などの設定検証リクエスト (2)「Swift 6対応の設定になっているか見て」などの特定設定の確認 (3) 新規プロジェクト作成後の設定レビュー (4)「フレームワークの設定が正しいか確認して」などのターゲット別設定確認
コードレビューを実施する際に使用。プルリクエストのレビュー、コード品質チェック、 セキュリティ検査、パフォーマンス分析を行う。「レビューして」「コードをチェック」 「品質を確認」などの指示で起動。
.github/prompts/*.prompt.md をレビューして改善提案を出す。frontmatterの妥当性、入力変数(${input:...})の設計、出力フォーマット固定、instructions/skillsへの参照（重複排除）、tools最小化、例の有無、命名規則、壊れやすい指示の検出を行い、レポートをdocs/prompt-review-report.mdに出力する。
Validate hledger journal files using the check and format scripts. Includes validation procedures, error checking, and pre-commit verification to ensure data integrity and consistency.
Provide a practical review of code changes, focusing on bugs, risk, security, and maintainability.
Verify Bun-specific patterns in backend code. Use when reviewing or writing backend TypeScript files to ensure Bun APIs are used instead of Node.js patterns.
审查代码质量、性能、安全性和设计模式。检查项目特定的反模式（降级处理、错误处理、类型安全）。使用此 Skill 来审查 PR、优化代码、或检查 TypeScript 类型安全性。
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that truly matter
Audit a specific iOS feature for bugs, dead code, and improvements
Adds detailed comments to code files. Invoke when user asks to add comments, document code, or explain code. RULES: Core methods=English, Tests=Chinese.
Comprehensive Swift/SwiftUI code review that runs view refactoring, performance audit, UI patterns, and concurrency checks on staged/unstaged changes. Use when reviewing Swift code changes before committing or when asked to review and refactor recent changes.
Perform static analysis on cvp/ modules for code quality reports. Use for code review or quality checks.
Use when designing R function APIs, reviewing R code for design issues, writing functions for R packages, or evaluating argument ordering and naming decisions. Does NOT cover: style/linting, error handling (rlang-conditions), CLI output (r-lib:cli), testing (testing-r-packages), CRAN compliance (cran-extrachecks).
Applique la philosophie "Broken Window" avec zéro tolérance pour les warnings/errors ESLint et TypeScript. JAMAIS désactiver les règles, TOUJOURS corriger la cause racine. À utiliser lors de la correction d'erreurs, warnings, ou quand l'utilisateur mentionne "eslint", "typescript error", "warning", "linting", "quality", "broken window", "@ts-ignore", "eslint-disable".
Review TypeScript code for type safety, null safety, and modern patterns. Enforces Studio-535 standards - no lazy any types, service layer pattern, proper error handling. Use when reviewing .ts/.tsx files or checking type definitions.
Enforce consistent Python typing (type hints + return types), concise Google-style docstrings, PEP 8/Black formatting, and unit tests when creating or editing Python code. Use when working on .py files, Python APIs, refactors, or bug fixes where maintainability and correctness matter.
