Analyze code and documentation for non-inclusive language, understanding context and intent before flagging issues. Use when reviewing code for biased terms, gendered language, or problematic terminology.
Validate skill documents against PMC skill design principles. Checks format ownership, composite skill structure, and internal consistency. CHECKS: 1. FORMAT OWNERSHIP - kb skill owns all format templates (kb/references/) 2. COMPOSITE STRUCTURE - Steps must have associated skills, stage announcements 3. INTERNAL CONSISTENCY - No gaps, broken references, or missing sections Use when: - Creating new skills - Reviewing existing skills - Periodic skill maintenance - User says "lint skills", "check skills", "validate skills"
Code review checklist covering security, performance, defensive programming, and testing anti-patterns. Use before merging PRs, after implementing features, or when reviewing code quality.
Security reminder hook that warns about potential security issues when editing files, including command injection, XSS, and unsafe code patterns
Performs a comprehensive pre-merge review of changes on the current branch. Use when the user wants to verify their work before merging, check PR readiness, or run a final validation of tests, types, lint, and PR metadata.
Apply the Agent OS standard for global conventions.
Conducts comprehensive frontend code reviews including React/Vue/Angular component analysis, TypeScript/JavaScript quality assessment, CSS/styling review, performance optimization, accessibility compliance, security vulnerabilities, and best practices validation. Produces detailed review reports with specific issues, severity ratings, and actionable recommendations. Use when reviewing frontend code, analyzing React/Vue/Angular components, checking JavaScript/TypeScript quality, validating CSS/SCSS, assessing web performance, or when users mention "review frontend code", "check React components", "analyze JavaScript", "review TypeScript", "validate accessibility", or "frontend code quality".
Comprehensive code review for quality, security, performance, and best practices
Run linters/formatters on changed files and apply safe, mechanical fixes. Use in Flow 3 and Flow 4.
Use when fixing TypeScript errors, implementing new features, or reviewing code. Ensures adherence to strict mode with noUncheckedIndexedAccess and exactOptionalPropertyTypes. Automatically applied to all TypeScript work.
Use when writing or modifying Python code to verify linting and type correctness before committing
リポジトリ全体を構造、コード品質、テスト、ドキュメントの観点から体系的にレビューし、優先度付きの改善レポートを生成する
Comprehensive code review of current branch using multi-agent verification across DDD/OOP compliance, DRY violations, clean code principles, architecture patterns, and test coverage
Perform systematic code review following {{sharedLib}}/{{projectName}} HMI standards and best practices. Use when reviewing pull requests, checking code quality, or validating implementations before commit. Checks MobX patterns, UI components, architecture, testing, and common pitfalls.
Run preflight checks and produce actionable install guidance for missing tools.
Removes unsupported or unknown compiler flags from build configurations.
C17/C23 best practices with Unity test framework, cppcheck, and Make/CMake build systems.
Scans codebases and dependencies for known vulnerabilities and security issues
Ensures clear understanding before any code changes, asks clarifying questions when requirements are ambiguous, discusses trade-offs, and protects the codebase from unintended alterations.
自分の書いたコードをレビューし、問題がゼロになるまで修正を繰り返す。 トリガー: (1) /review コマンド (2)「レビューして」「コードレビュー」等の発話 (3) 実装完了後
