code-review
Revisa código en PRs o cambios. Usar para code review, analizar diffs, identificar problemas de calidad, seguridad o performance, y sugerir mejoras.
obsidian-markdown-structure
Validate and enforce markdown document structure including frontmatter positioning, heading hierarchy, and content organization. Use when creating or validating markdown files.
rustfeed-quality
rustfeed プロジェクトのコード品質チェック(cargo fmt、clippy、test、doc)を実行します。コード品質確認、コミット前チェック、CI/CD検証時に使用します。
technical-review
Conduct a detailed technical review of recent changes or a specific feature. Use when user says "review PR", "code review", or "review [scope]". Analyzes for logic errors, bugs, style issues, and performance. Fixes critical/high issues automatically.
rails-production-release
Checks for breaking changes in API serializers before production release. Use when reviewing PRs to production branch.
quality-check
Run quality checks on code changes. Use after implementation, before commits, or when the user mentions review, check, validate, or lint.
arc-package-validator
Validate Swift Packages against ARC Labs Studio standards defined in ARCKnowledge. Use when checking package compliance, auditing structure, reviewing before release, or verifying ARCDevTools integration. Triggers on requests like "validate package", "check ARC standards", "is this package ready", "audit ARCPackage", "package compliance check", "review package structure".
pattern-enforcement
Enforce architectural patterns with ESLint rules. Block infra imports, enforce object params, prevent server/client leaks.
flow-conventions-folder-structure
Validate and fix folder structure for Output SDK workflows. Use to ensure migrated workflows follow the correct structure conventions.
contrast-fixer
This skill should be used when detecting and fixing color contrast issues in the codebase. It finds dark text on dark backgrounds and light text on light backgrounds, then provides fixes to ensure proper readability. Uses an automated Python script for detection and provides Tailwind-specific fix recommendations.
frontend-code-review
Trigger when the user requests a review of frontend files (e.g., `.tsx`, `.ts`, `.js`). Support both pending-change reviews and focused file reviews.
backend-code-review
Conducts comprehensive backend code reviews including API design (REST/GraphQL/gRPC), database patterns, authentication/authorization, caching strategies, message queues, microservices architecture, security vulnerabilities, and performance optimization for Node.js, Python, Java, Go, and C#. Produces detailed review reports with specific issues, severity ratings, and actionable recommendations. Use when reviewing server-side code, analyzing API implementations, checking database queries, validating authentication flows, assessing microservices architecture, or when users mention "review backend code", "check API design", "analyze server code", "validate database patterns", "security audit", "performance review", or "backend code quality".
complexity-check
Enforce code complexity limits and quality standards in TapScore backend. Use when writing or reviewing backend code to ensure method size limits, nesting depth, naming conventions, and use of domain constants are followed.
code-review-checklist
Code review criteria covering security, performance, quality standards, and issue prioritization for thorough code analysis.
best-practices
Always ensure the code and design follow the absolute latest industry standards, premium UI/UX trends, and library documentation.
typescript-strict
Enforces strict TypeScript rules and patterns. Use when refactoring code to be type-safe or fixing TS errors.
check-code-complete
Verify code has no TODOs, stub implementations, or dead code before merge
code-standards
Load when reviewing code, writing code examples, or ensuring code quality. Contains coding standards for Python, JavaScript, SQL, and general best practices for publication-quality code.
documentation-parity-patterns
Validates code-documentation parity using tree-sitter static analysis. Use when user asks about documentation validation, doc parity, checking if docs are up to date, or whether code matches documentation.
quality-automation
タスク完了時の自動レビューを実装。手動チェックを削減し、一貫性のある品質を維持。