GitHub
command-naming-conventions
コマンド命名規則（動詞ベース命名/kebab-case/名前空間/発見可能性）を整理し、一貫した命名設計と見直しを支援するスキル。 命名ルール、チェックリスト運用、検証手順を一貫して整理する。 Anchors: • The Pragmatic Progr...
Skills IA tools code quality
Découvrez les skills tools code quality, comparez leurs dépôts et consultez leurs instructions.
Catégories: tools code quality
tools code quality Effacer les filtres
Explorer
GitHub
code-smell-detection
コードスメルとアーキテクチャ・アンチパターンを整理し、レビューと改善対象の特定を支援するスキル。 クラス/メソッドのスメル検出、改善優先度の整理、レポート化を扱う。 Anchors: • Clean Code (Robert C. Martin) / 適...
GitHub
dependency-auditing
依存関係の脆弱性検出、評価、修正計画を体系化するスキル。 CVSS評価と修正優先度を整理し、継続的な監査を支援する。 Anchors: • CVSS v3.1 Specification / 適用: 重大度評価 / 目的: 優先度の整合性 • The Pragmatic Prog...
GitHub
eslint-configuration
ESLint設定ファイルの作成・更新、ルールセット選択、パーサー設定、プラグイン統合を行う専門スキル。 プロジェクトの言語・フレームワークに最適化された設定を生成し、Prettierとの競合解決も行う。 Anchors: • ESLint公式...
GitHub
senior-code-review
Senior engineer code review for PRs, diffs, and code snippets focusing on security vulnerabilities, OWASP compliance, performance bottlenecks, maintainability, error handling, and architectural patterns
GitHub
refactoring
Refactoring assessment and patterns. Use after tests pass (GREEN phase) to assess improvement opportunities.
GitHub
typescript-strict
TypeScript strict mode patterns. Use when writing any TypeScript code.
GitHub
precommit
Running precommit checks and build validation. ALWAYS use after ANY code changes.
GitHub
comment-cleanup
Guidelines for comments in code. Use when adding, editing, or removing comments.
GitHub
justfile-style
Style guidelines for justfile recipe documentation. Use when writing or editing justfiles to ensure consistent and concise documentation.
GitHub
code-quality
Code quality guidelines. ALWAYS use skill for ANY code changes.
GitHub
php-best-practices
PHP 8.5+ modern patterns, PSR standards, and SOLID principles. Use when reviewing PHP code, checking type safety, auditing code quality, or ensuring PHP best practices. Triggers on "review PHP", "check PHP code...
GitHub
rules-repo-conventions
Apply Rules Repository conventions and forward-only workflow. Use when generating or editing docs, prompts, or code in projects that consume this repository or when this repository is the active workspace. Ensu...
GitHub
policyengine-review-patterns
PolicyEngine code review patterns - validation checklist, common issues, review standards
GitHub
policyengine-standards
PolicyEngine coding standards, formatters, CI requirements, and development best practices
GitHub
multi-ai-code-review
멀티 AI 코드 리뷰 오케스트레이터. Claude, Codex, Gemini, Droid를 조율하여 종합적 코드 리뷰 수행. "멀티 AI 리뷰", "코드 리뷰", "종합 리뷰" 요청 시 활성화됩니다.
GitHub
pr-review-loop
PR 리뷰 대기 및 자동 수정 루프. "리뷰 대기", "리뷰 반영 대기", "자동 리뷰 수정", "review loop" 요청 시 활성화됩니다.
GitHub
csharp-code-style
C# code style and naming conventions based on POCU standards. Covers naming rules (mPascalCase for private, bBoolean prefix, EEnum prefix), code organization, C# 9.0 patterns. Use PROACTIVELY for C# code review...
GitHub
codex-cli
OpenAI Codex CLI fundamentals for code analysis, review, and validation. Use when (1) executing codex commands for code review/analysis, (2) configuring models (gpt-5.2-codex/gpt-5.2/gpt-5.1-codex-max/codex-min...
GitHub
review-scope
Use before code review - determine if change is minor (review new code only) or major (review impacted code too)
GitHub
apply-all-findings
Use after code review - implement ALL findings; any finding not fixed MUST have tracking issue created; no finding disappears without trace
GitHub
style-guide-adherence
Use when writing code - follow Google style guides where available, otherwise follow established best practices for the language
GitHub
typescript-patterns
TypeScript best practices, strict typing patterns, and type safety strategies. Use when implementing TypeScript code with focus on type correctness and maintainability.
GitHub
implementation-safety
Production-ready safety checklists for Rails implementation. Covers nil safety, ActiveRecord patterns, security vulnerabilities, error handling, and performance. Use before marking any file complete during impl...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.