All categories
Code Review & Quality
Code review, refactoring, debugging, maintainability, and engineering quality
- 14,947
- 623
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse code review & quality skills
Showing 265–288 of 14,947 skills
- Coding StandardsRust coding standards (Japanese comments required, error handling, logging, naming conventions). Use when writing new code, adding error handling, logging, fixing errors, asking about coding style, thiserror, tracing, naming conventions, or code review.Votes: 0GitHub stars: 2
- Coding Standards 8Enforces consistent coding standards across the codebase including naming conventions, code organization, and documentation requirements. Use when writing new code, reviewing pull requests, or refactoring existing code.Votes: 0GitHub stars: 2
- Coding Standards 3Detects code smells, anti-patterns, and readability issues. Use when implementing features, reviewing code, or refactoring.Votes: 0GitHub stars: 2
- Coding Standards 12PHP coding standards (PSR-12, PHPDoc, type hints) for any PHP projectVotes: 0GitHub stars: 2
- Coding PrinciplesThis skill provides language-agnostic coding principles for maintainability, readability, and quality. Automatically loaded when implementing features, refactoring code, reviewing code quality, or when the user mentions "clean code", "best practices", "code quality", or "maintainability".Votes: 0GitHub stars: 2
- Coding Principles 2Universal coding principles and best practices for maintainable softwareVotes: 0GitHub stars: 2
- Coding ConventionsProvides coding style rules for Python and PowerShell. Apply when writing, editing, reviewing, or debugging code.Votes: 0GitHub stars: 2
- Coding Best PracticesGeneral coding principles for writing clean, maintainable code. Triggers on any development work, code reviews, refactoring, or when adding dependencies. For frontend/React code, also apply web-ui-best-practices and react-best-practices.Votes: 0GitHub stars: 2
- Coding 1Use when performing coding tasks (implement features, fix bugs, refactor code). Orchestrates language detection, mode switching (normal/autopilot/full-auto), quality enforcement, and verification.Votes: 0GitHub stars: 2
- Codex ReviewerUse when running Codex as an independent reviewer. Focus on actionable, prioritized findings.Votes: 0GitHub stars: 2
- Codex ReviewCodex CLI（read-only）を用いて、レビュー→Claude Code修正→再レビュー（ok: true まで）を反復し収束させるレビューゲート。仕様書/SPEC/PRD/要件定義/設計、実装計画（PLANS.md等）の作成・更新直後、major step（>=5 files / 新規モジュール / 公開API / infra・config変更）完了後、および git commit / PR / merge / release 前に使用する。キーワード: Codexレビュー, codex review, レビューゲート.Votes: 0GitHub stars: 2
- Codex Review 9Self-review loop for code changes. Use when Codex edits files or prepares a PR and should run `codex exec --sandbox workspace-write review --base BASE`, fix findings, and re-run until clean (max 10). Also run tests when a test command is configured or detectable.Votes: 0GitHub stars: 2
- Codex Review 6Delegates code review to OpenAI Codex CLI. Use when user says "코드 리뷰해줘", "Codex한테 리뷰 맡겨", "PR 검토해줘", "코드 품질 체크", "리팩토링 제안해줘", "second opinion", or asks for code review, refactoring suggestions.Votes: 0GitHub stars: 2
- Codex Review 12Codex CLI（read-only）を用いて、レビュー→Claude Code修正→再レビュー（ok: true まで）を反復し収束させるレビューゲート。仕様書/SPEC/PRD/要件定義/設計、実装計画（PLANS.md等）の作成・更新直後、major step（>=5 files / 新規モジュール / 公開API / infra・config変更）完了後、および git commit / PR / merge / release 前に使用する。キーワード: Codexレビュー, codex review, レビューゲート.Votes: 0GitHub stars: 2
- Codex Review 10Professional code review skill for Claude Code. Automatically collects file changes and task status. Triggers when working directory has uncommitted changes, or reviews latest commit when clean. Triggers: code review, review, 代码审核, 代码审查, 检查代码Votes: 0GitHub stars: 2
- Codex OracleDelegate complex reasoning, planning, or deep analysis tasks to OpenAI's GPT-5.2-Codex model. Use when tasks require extended thinking, multi-step planning, or when you need a second opinion on complex problems.Votes: 0GitHub stars: 2
- Codex IntegrationThis skill provides guidance on using OpenAI's Codex CLI for detail-oriented code analysis. Use when the user explicitly invokes "/codex", asks to "use codex", "run codex", "have codex review", or when Claude determines that Codex's sharp-eyed analysis would complement its work on code review, bug hunting, or planning tasks.Votes: 0GitHub stars: 2
- Codex ConsultThis skill should be used when the user asks to "consult Codex", "ask Codex for advice", "get implementation suggestions from Codex", "codexに相談", "codexにきいて", "実装方針を相談", "アーキテクチャをcodexに聞く", or needs deeper analysis using OpenAI's Codex model for complex implementation decisions, architecture design, or code review that benefits from extended reasoning.Votes: 0GitHub stars: 2
- Codex Agent 1MANDATORY for code review - must use Codex CLI for all code reviews, then apply fixes based on Codex feedback. Also use for cross-verification, debugging, and getting alternative implementations.Votes: 0GitHub stars: 2
- Codex 6Guide for using Codex CLI for code reviews and specs.Votes: 0GitHub stars: 2
- Codex 20AI peer review via OpenAI Codex CLI. Use when reviewing code changes, validating technical decisions, comparing implementation approaches, or getting a second opinion on architecture choices. Triggers on /codex, /codex-review, or auto-triggers when presenting significant alternatives to user.Votes: 0GitHub stars: 2
- Codex 19Use when Claude Code needs a second opinion, verification, or deeper research on technical matters. This includes researching how a library or API works, confirming implementation approaches, verifying technical assumptions, understanding complex code patterns, or getting alternative perspectives on architectural decisions. The agent leverages the Codex CLI to provide independent analysis and validation.Votes: 0GitHub stars: 2
- Codex 14Use the OpenAI Codex CLI to analyze code, plan, and perform other tasks.Votes: 0GitHub stars: 2
- Codereview RoastedBrutally honest code review in the style of Linus Torvalds, focusing on data structures, simplicity, and pragmatism. Use when you want critical, no-nonsense feedback that prioritizes engineering fundamentals over style preferences.Votes: 0GitHub stars: 2