pre-release
Run all validation checks before tagging a new release
code-review-assistant
系统化的程序码审查检查清单和提交前品质关卡。 使用时机：审查 pull request、检查程序码品质、提交程序码前。 关鍵字：review, PR, pull request, checklist, quality, commit, 审查, 检查, 簽入。
release-check
Pre-release integrity check. Verify package consistency for API changes and spec updates. Use for release check, version update, documentation consistency, pre-release verification.
base-rules
General development rules including comment length, testing protocol, and command aliasing (puro).
secrets-detector
Detects hardcoded secrets, API keys, passwords, and credentials in source code. Use when checking for leaked secrets, credential exposure, or before committing code.
code-review-assistant
系統化的程式碼審查檢查清單和提交前品質關卡。 使用時機：審查 pull request、檢查程式碼品質、提交程式碼前。 關鍵字：review, PR, pull request, checklist, quality, commit, 審查, 檢查, 簽入。
codereview-roasted
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.
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
frontend-developer
Use when implementing frontend code, optimizing performance, or ensuring strict adherence to documentation/references.
docusaurus-config
Use when working with docusaurus.config.js/ts files to validate or modify Docusaurus configuration
google-style-guide
Use when writing or reviewing technical documentation to follow Google's documentation style guide - https://developers.google.com/style
code-formatter
Otomatik kod formatlama, Prettier/ESLint entegrasyonu ve kod stil tutarlılığı rehberi.
code-quality-workflow
Mandatory code quality workflow that must run after ANY code changes. Use after creating/editing files, before commits, or when fixing errors. Keywords - testing, linting, formatting, typecheck, quality gates, workflow.
code-quality
Code quality guidelines including naming, structure, and maintainability. This skill should be used when writing or reviewing code to ensure it meets quality standards. Use proactively when discussing naming conventions, code smells, readability, Sandi Metz rules, method length, class size, comments, refactoring for clarity, or maintainability concerns. (user)
ruby-coder
This skill guides writing of new Ruby code following modern Ruby 3.x syntax, Sandi Metz's 4 Rules for Developers, and idiomatic Ruby best practices. Use when creating new Ruby files, writing Ruby methods, or refactoring Ruby code to ensure adherence to clarity, simplicity, and maintainability standards.
rails-conventions
Rails code patterns and conventions following rubocop-rails-omakase style.
claude-rules-authoring
This skill should be used when creating rule files, organizing conventions, or when ".claude/rules/", "FORMATTING.md", "create rule", or "project conventions" are mentioned.
rails-refactorer
Use proactively when refactoring Ruby on Rails code. Applies Rails conventions, Sandi Metz rules, and idiomatic Ruby patterns while maintaining test coverage.
grey-haven-commit-format
Format commit messages according to Grey Haven Studio's actual commitlint configuration (100 char header, lowercase subject, conventional commits). Use when creating git commits or reviewing commit messages.
design-spec-auditor
Verify code implementation aligns with design specifications. Use after implementing features, during code reviews, or when refactoring to ensure architectural compliance. Compares design docs with actual code.
