python-quality
Python品質チェック。pytest/mypy/Black実行時に使用。「Pythonの品質チェック」「静的解析」で起動。
check-and-fix
Run TypeScript checks and fix all errors (project)
prnd-layered-python-code-reviewer
Review Python code changes with a focus on layered architecture boundaries, DI/DIP, configuration validation, typing quality (mypy/flake8 readiness), naming/docstring accuracy, and testability. Use when asked to “code review”, “PR review”, or “리뷰해줘” to prevent repeat feedback on architecture regressions and low-signal changes.
code-review
Review code for correctness, design quality, and complexity using principles from "A Philosophy of Software Design." Use this skill when reviewing pull requests, code changes, diffs, or when asked to find bugs, evaluate code quality, identify design problems, or provide feedback on architecture and abstractions.
maverick-python-peps
Python Enhancement Proposals (PEPs) and style guidelines
python
Advanced Python development with architecture expertise and automated code quality enforcement. Use when developing Python applications, libraries, or scripts that require high code quality, type safety, best practices, and professional architecture patterns. Includes automated linting with Ruff, type checking with MyPy, security scanning with Bandit, and comprehensive testing. Apply for tasks involving Python code creation, refactoring, quality checks, project initialization, or implementing design patterns.
typescript-patterns
Best practices for TypeScript types, interfaces, assertions, and type safety. Use when writing or reviewing TypeScript code.
eld-ground-pr-review
PCE (Process-Context Engine) を活用したPRレビュースキル。Compile→Execute→Captureのフローでレビューを行い、知見を蓄積する。 LDE(Law-Driven Engineering)との統合により、Law遵守・Grounding検証も実行。 トリガー条件: - 「PRをレビューして」 - 「PR #123 を確認して」 - 「変更内容をチェックして」 - gh pr view の結果を見た後 - 「Law観点でレビューして」
code-style
Enforce SOLID principles and clean code practices to improve readability, maintainability, and code quality. Use when writing, refactoring, or reviewing code.
type-safety
Fixes TypeScript type safety issues including unsafe member access, assignments, returns, calls, and arguments. Use when encountering @typescript-eslint/no-unsafe-* errors or when working with unknown/any types.
validate-all
Run comprehensive validation on all site content. Use for daily health checks or before deployment.
c99-code-review
Review C99 code for compliance with HBF's strict coding standards including compiler warnings, Linux kernel style, and licensing constraints. Use when reviewing or writing C code in this project.
strict-typescript
Enforce patterns with TypeScript beyond strict:true. Include noUncheckedIndexedAccess, erasableSyntaxOnly, ts-reset, and type-fest. Advanced type patterns and ESLint enforcement.
ai-readability-analysis
コードのAI可読性を分析し、生成AIがバグ修正や変更を行う際に苦戦する原因となる問題を特定するスキル。 以下の場合に使用する: (1) 「AIが修正しやすいコードか分析して」「AI可読性を診断して」と依頼された時 (2) バグ修正や変更作業が難航している原因を調査したい時 (3) コードベースのAIフレンドリー度を評価したい時 (4) リファクタリング優先度を決めたい時 分析観点:コンテキストウィンドウ問題、命名・表現問題、構造・設計問題、テスト・検証問題、ドキュメント問題、LLM特有の苦手パターン
code-review
Realiza revisão de código completa seguindo as diretrizes Bewear, verificando padrões de arquitetura, TypeScript, React, Next.js, segurança e boas práticas. Use para revisar PRs ou código antes de merge.
tdd-discipline
Use when implementing features, fixing bugs, or writing any production code - enforces RED-GREEN-REFACTOR cycle where tests must fail before writing implementation code. Activates before coding begins.
code-conventions
Defines project-wide code conventions for magic number elimination, constant usage, performance optimization, and type safety. Use when implementing, testing, or reviewing code to ensure consistency across the codebase.
python-lint
Validate and auto-fix Python linting, formatting, and type issues using ruff and ty
compliance-check-agent
Verifies code and configurations comply with security standards and regulations