Senior engineer code review for PRs, diffs, and code snippets focusing on security vulnerabilities, OWASP compliance, performance bottlenecks, maintainability, error handling, and architectural patterns
Automatically detect and fix Python deprecation warnings in codebases, including datetime.utcnow(), and other common deprecated patterns. Supports extensible pattern matching for future deprecations.
README quality standards for engaging, accessible, scannable content including problem-solution hooks, plain language (no unexplained jargon), acronym context, paragraph limits (≤5 lines), benefits-focused language, visual hierarchy, and progressive disclosure. Essential for creating effective README files that welcome and guide users.
コードスメルとアーキテクチャ・アンチパターンを整理し、レビューと改善対象の特定を支援するスキル。 クラス/メソッドのスメル検出、改善優先度の整理、レポート化を扱う。 Anchors: • Clean Code (Robert C. Martin) / 適用: コード品質レビュー / 目的: 意図の明確化 • Refactoring (Martin Fowler) / 適用: スメル検出と改善 / 目的: 安全な修正 • Working Effectively with Legacy Code (Michael Feathers) / 適用: 改善対象の特定 / 目的: リスク最小化 Trigger: Use when detecting code smells, identifying refactoring targets, analyzing technical debt, or documenting anti-patterns. code smells, anti-patterns, refactoring targets, technical debt, architecture review
TypeScript and React-specific code review guidelines covering type safety, React anti-patterns, performance issues, accessibility concerns, and security vulnerabilities. Use when reviewing TypeScript/React code changes for quality and best practices.
Link validation standards for markdown links including format requirements, path validation, broken link detection, and external link verification
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
Review code for quality, bugs, security, and improvements. Use when self-reviewing before commit, reviewing PRs, or debugging issues.
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
Verify dependency structure and architecture health for SDL3 HammerEngine. Detects circular dependencies, excessive coupling, layer violations, header bloat, and provides dependency graph visualization. Ensures adherence to layered architecture (Core→Managers→States→Entities). Use monthly, after major refactors, or when investigating compile time issues.
Analyze Gradle dependencies for outdated versions, known CVEs, unnecessary transitive dependencies, and version conflicts
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
Runs comprehensive code quality checks for SDL3 HammerEngine including compilation warnings, static analysis (cppcheck, clang-tidy), coding standards validation, threading safety verification, and architecture compliance. Use before commits, pull requests, or when the user wants to verify code meets project quality standards.
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
TypeScript coding standards and design principles. Use when writing new code, reviewing code, refactoring, or when guidance is needed on naming conventions, documentation (JSDoc), immutability, strict typing, testing patterns, or design principles like avoiding over-abstraction.
Comprehensive parallel code review using 5 specialized subagents: general, architectural, TypeScript, product/vision, and TDD/beads compliance
Performs critical code reviews with a skeptical mindset, assuming the author cannot be fully trusted. Evaluates code quality, architecture, testing, requirements, and production readiness. Use after completing significant code changes or before merging.
Validates logs against type-specific schemas checking frontmatter, structure, and required fields
Run full pre-commit workflow for Go code. Use when preparing to commit Go changes, before creating pull requests, or ensuring code quality.
