code-review-checklist
Comprehensive code review checklists for backend and frontend code.
Comprehensive code review checklists for backend and frontend code.
コマンド命名規則(動詞ベース命名/kebab-case/名前空間/発見可能性)を整理し、一貫した命名設計と見直しを支援するスキル。 命名ルール、チェックリスト運用、検証手順を一貫して整理する。 Anchors: • The Pragmatic Programmer (Andrew Hunt, David Thomas) / 適用: 命名規則の一貫性 / 目的: 実践的な命名の安定化 • Clean Code (Robert C. Martin) / 適用: 意図が伝わる命名 / 目的: 自己説明性の向上 Trigger: Use when defining command naming conventions, reviewing naming consistency, or designing namespace structures. command naming, kebab-case, verb-based naming, namespace design, discoverability
主要コードスタイルガイドの比較と適用を整理し、チーム規約の統一と移行を支援するスキル。 Airbnb/Google/Standardの選定、カスタマイズ、移行計画を扱う。 Anchors: • Clean Code (Robert C. Martin) / 適用: 命名と意図の明確化 / 目的: 可読性の向上 • Style Guide Comparison / 適用: ガイド選定 / 目的: 適合性評価 • Migration Patterns / 適用: 移行計画 / 目的: 変更影響の最小化 Trigger: Use when selecting or migrating style guides, unifying team conventions, or customizing linting rules. code style guide, ESLint config, Prettier rules, migration, coding conventions
TypeScript best practices, strict typing patterns, and type safety strategies. Use when implementing TypeScript code with focus on type correctness and maintainability.
静的コード解析と品質メトリクスの設定、複雑度評価、Code Smell検出を支援するスキル。 品質基準の策定から改善優先度付けまでを一貫して整理する。 Anchors: • Clean Code / 適用: 品質基準 / 目的: コード品質の判定 • Code Complete / 適用: 複雑度管理 / 目的: 認知負荷の低減 Trigger: Use when configuring static analysis, defining quality gates, measuring complexity, or triaging code smells. static analysis, complexity metrics, code smells, quality gate
This skill should be used for Python idioms, type hints, async/await, pytest, Django, Flask, FastAPI, Python web frameworks, pandas, data processing
ESLintとPrettierの統合とフォーマット自動化の専門知識を提供します。 責務分離、競合解決、エディタ統合、保存時自動実行を設計します。 Anchors: • The Pragmatic Programmer (Hunt, Thomas) / 適用: 実践的改善アプローチ、自動化の価値判断 / 目的: ツール統合の最適化指針 • Prettier公式ドキュメント / 適用: 設定オプション選択、デフォルト値理解 / 目的: opinionatedツールの適切な活用 • ESLint + Prettier統合ガイド / 適用: 責務分離、競合回避パターン / 目的: 適切な統合設計 Trigger: Use when setting up Prettier with ESLint, resolving formatting conflicts, configuring editor integration, or implementing automated formatting workflows. prettier integration, eslint prettier conflict, code formatting setup, auto format on save, prettier eslint setup, formatting automation
ESLint設定ファイルの作成・更新、ルールセット選択、パーサー設定、プラグイン統合を行う専門スキル。 プロジェクトの言語・フレームワークに最適化された設定を生成し、Prettierとの競合解決も行う。 Anchors: • ESLint公式ドキュメント / 適用: ルール定義・設定形式 / 目的: 仕様準拠 • typescript-eslint / 適用: TypeScript設定 / 目的: 型チェック統合 • eslint-plugin-react / 適用: React固有ルール / 目的: JSX最適化 • Prettier連携ガイド / 適用: 競合解決 / 目的: フォーマッタ共存 Trigger: Use when creating or updating ESLint configuration, selecting rulesets, configuring parsers, integrating plugins, or resolving Prettier conflicts. eslint, eslintrc, flat config, typescript-eslint, react eslint, prettier conflict, lint rules, code quality
Code quality automation for linting and formatting. Provides ESLint, Prettier, Biome setup, CI/CD integration, pre-commit hooks, and tool migration strategies for consistent code style enforcement. Anchors: • ESLint Official Docs / Apply: Rule configuration, plugin integration / Purpose: Correct API usage and best practices • Prettier Philosophy / Apply: Opinionated formatting / Purpose: Minimize configuration bikeshedding • Biome Performance Model / Apply: Rust-based tooling / Purpose: Optimize development workflow speed Trigger: Use when setting up linting/formatting for new projects, integrating code quality into CI/CD, configuring pre-commit hooks, or migrating between tools. eslint, prettier, biome, lint, format, pre-commit, husky, lint-staged, code quality
Systematically explore codebases using search and LSP to understand code structure, intent, and behavior. READ_ONLY mode - no file modifications.
Validates logs against type-specific schemas checking frontmatter, structure, and required fields
Setup ESLint with Airbnb TypeScript config and Prettier formatter for code quality enforcement. Use when setting up new project, adding linting/formatting, or configuring code quality tools (e.g., "Setup ESLint and Prettier", "Configure code quality", "Add Airbnb linter").
Review and validate WordPress documentation against official style guide standards. Use when reviewing documentation for WordPress core, themes, plugins, or related projects. Checks compliance with voice/tone, accessibility, inclusivity, code formatting, and technical writing standards.
Automatically reviews code changes against issue/spec at evaluate phase start to ensure implementation completeness
Validates documentation against type-specific rules and schemas loaded dynamically, checking frontmatter, structure, content, and schema compliance
Review code changes for game/engine systems with a focused Game Systems Engineer mindset. Use when the user asks to review code, check consistency, or validate changes against AGENTS.md standards, especially for C++ engine, threading, performance, or systems behavior.
Runs complete build validation pipeline for SDL3 HammerEngine including Debug build, smoke test execution, core test suite, and summary report generation. Use when the user wants to quickly validate their changes, check if the codebase is in a good state, or run the standard daily validation workflow.
依存関係の脆弱性検出、評価、修正計画を体系化するスキル。 CVSS評価と修正優先度を整理し、継続的な監査を支援する。 Anchors: • CVSS v3.1 Specification / 適用: 重大度評価 / 目的: 優先度の整合性 • The Pragmatic Programmer / 適用: 自動化と継続改善 / 目的: 監査の継続性 • OWASP Dependency-Check / 適用: 依存監査 / 目的: 脆弱性検出の標準化 Trigger: Use when auditing dependencies, evaluating vulnerability reports, prioritizing remediation, or integrating security scans into CI/CD. dependency audit, CVE, GHSA, CVSS, npm audit, pnpm audit, security scanning
Develop, maintain, and audit Go analyzers (go/analysis). Use when creating/updating analyzers, suggested fixes, analysistest golden files, or integration analyzer harnesses.