Validates code changes against safe-formdata's boundary-focused design principles. Detects violations of "keys are opaque", "no silent behavior", "no inference", and "explicit issue reporting". Use when reviewing PRs, implementing features, or checking adherence to design rules.
Rails code style conventions. Use when working with Rails projects, running commands, or writing Rails code.
Experienced technical lead specializing in code reviews for Flutter applications. Use for reviewing code quality, security vulnerabilities, performance issues, architecture violations, and ensuring adherence to best practices before merging.
Always use this skill when writing or editing code of any sort!
Explicit accessibility enhancement and validation for generated UI code. Only invoke when user explicitly requests accessibility review, a11y enhancement, or WCAG compliance check.
Run static analysis, security scans, and dependency checks on .NET code. Use when task involves code quality, security audits, or vulnerability detection.
Validates specs have required frontmatter, links, and compliance. Use before commits or during code review.
Activates when errors occur during execution. Provides self-correction patterns for immediate error fixing without verbose explanations or apologies.
NASA/JPL Power of 10 coding rules for safety-critical C code. Use when writing embedded C firmware, safety-critical systems, aerospace code, or any project requiring high reliability. Enforces static analysis, bounded loops, no dynamic memory.
Use when the user asks to review code or a pull request - performs focused review checking for obvious defects only, provides minimal feedback with clear approval/rejection format
PREFERRED METHOD for Qodana scans. Always delegate to local-qodana-reviewer sub-agent when user mentions Qodana, code quality scan, static analysis locally, or requests to run Qodana. Do NOT run qodana commands directly.
Analyze code comments for accuracy, completeness, and long-term maintainability. Use after adding documentation, before finalizing PRs with comment changes, or when reviewing existing comments for technical debt.
Validate and maintain YAML/JSON configuration files. Use when asked to check config consistency, add new mappings, update blocklists, or ensure configuration integrity.
Python code style and type hinting patterns. Use when writing or reviewing Python code to ensure consistent, modern type annotations and clean code structure. Covers modern type hints, import organization, comment practices, and docstring conventions.
Configura linting automático com pre-commit hooks e CI/CD para projetos Python
Evaluate code review quality and provide feedback on review effectiveness and thoroughness
Strict design rules and style preferences for the frontend.
Enforces OpenSpec authoring conventions including metadata blocks, section ordering, requirement/scenario structure, and validation steps.
ALWAYS use this skill immediately after running 'ansible-galaxy init' to create a new Ansible role. Also use when the user asks to fix ansible-lint errors or when ansible-lint output shows fixable issues like yaml[comments], schema[meta], meta-incorrect, name[play], or role-name[path] violations.
Compact Python style guide. Key conventions for clean, typed, documented code.
Safely refactor TypeScript code while maintaining type safety and test coverage. Includes verification steps.
Activates after code changes to suggest or run verification steps. Provides test-after-action patterns for different file types and frameworks.
言語共通のコードレビュースキル。コメント最適化、マジックナンバー検出、構造改善のレビューを実施。コードレビュー、PRレビュー、コード品質チェックを依頼された際に使用。
