dart-dart-fix
To apply automated Dart fixes, run `dart fix --apply` on the given roots to resolve suggested changes.
yaml-config-helper
Validate, format, and troubleshoot YAML configuration files
conflict-resolution
Handle Superwiser rule conflicts when search_rules, list_rules, or load_preferences shows "⚠️ CONFLICT [id]"
refactor-import-hygiene
Audit Python imports to preserve semantic context and prevent shadowing after refactors. Prefer namespace-first imports over direct symbol imports for generic identifiers.
validate-typescript
Run TypeScript compiler type-checking (tsc --noEmit) to validate type safety and catch type errors. Returns structured output with error counts, categories (type/syntax/import errors), and affected files. Used for quality gates and pre-commit validation.
neovim-debugging
Debug Neovim/LazyVim configuration issues. Use when: user reports Neovim errors, keymaps not working, plugins failing, or config problems. Provides systematic diagnosis through hypothesis testing, not just checklists. Think like a detective narrowing down possibilities.
markdownlint
This skill should be used when users need to format, clean, lint, or validate Markdown files using the markdownlint-cli2 command-line tool. Use this skill for tasks involving Markdown (including Quarto Markdown `.qmd`) file quality checks, automatic formatting fixes, enforcing Markdown style rules, or identifying Markdown syntax issues.
shellcheck-configuration
シェルスクリプト品質のためのShellCheck静的解析の設定と使用をマスター。リンティングインフラの設定、コード問題の修正、またはスクリプトの移植性の確保時に使用してください。
go-uber-style
Use this skill when writing Go code following the Uber Go Style Guide. Provides comprehensive guidance on idiomatic Go patterns, error handling, concurrency safety, performance optimization, and test-driven development. Covers all critical Uber Go rules including channel sizing, goroutine management, interface design, and proper error handling. Appropriate for any task involving .go files, Go code reviews, refactoring, or implementing Go best practices.
validate-typescript
Run TypeScript compiler type-checking (tsc --noEmit) to validate type safety and catch type errors. Works with any TypeScript project. Returns structured output with error counts, categories (type/syntax/import errors), and affected files. Used for quality gates and pre-commit validation.
review-scope
Use before code review - determine if change is minor (review new code only) or major (review impacted code too)
sast-configuration
アプリケーションコードでの自動脆弱性検出のための静的アプリケーションセキュリティテスト（SAST）ツールを設定します。セキュリティスキャンの設定、DevSecOps実践の実装、またはコード脆弱性検出の自動化時に使用してください。
simplifying-ruby-code
Identify over-engineering in Ruby - prefer simple data structures (Hash, Struct, Data) and pure functions over unnecessary classes
systematic-code-review
Structured code review framework using Conventional Comments for clear, actionable feedback.
markdown-quality
Use when creating or editing any markdown file (.md) - ensures consistent formatting and zero linting violations through mandatory validation
format-bicep
Formats Bicep code for readability and consistency.
frontend-debug-linting
Quality gates for frontend code. ALWAYS use after writing React/Next.js code and before delivery. Covers: ESLint linting, TypeScript type-checking, Prettier formatting, browser console debugging. Catches errors before they reach users.
style-guide-adherence
Use when writing code - follow Google style guides where available, otherwise follow established best practices for the language
code-quality-standards
Code quality standards including SOLID principles, design patterns, code smells, refactoring techniques, naming conventions, and technical debt management. Use when reviewing code, refactoring, ensuring quality, or detecting code smells.
code-review
Comprehensive code review checklist. Use when asked to review code, PRs, pull requests, or before committing changes.
