Discover tools code quality skills, compare source repositories and read the instructions for each workflow.
Find and replace code patterns structurally using ast-grep. Use when you need to match code by its AST structure (not just text), such as finding all functions with specific signatures, replacing API patterns a...
Cross-language linter autofix commands and common fix patterns for biome, ruff, clippy, shellcheck, and more.
Structured code review approach covering security, quality, performance, and consistency.
Pre-commit security validation and secret detection. Runs detect-secrets scan and audit workflow, validates secrets baseline, and integrates with pre-commit hooks to prevent credential leaks. Use when user ment...
评审 Project Guardrails/工程规范。用于在 LLD/实现前检查 Guardrails 的完整性、可执行性、一致性与可验证性，给出准出结论。
Run the local "ready for review" gate before asking for human review or opening a PR. Use to (1) run the repo’s lint/typecheck/tests (prefer the same commands CI runs), then (2) run `codex review` as a final au...
Reviews code changes for complexity and simplification opportunities. Use before creating PRs or when reviewing changesets.
Pre-commit checklist that reviews test coverage, simplifies code, reviews for complexity, and validates changes work.
Reviews test coverage and testing strategy for recent code changes. Use before creating PRs to ensure changes are well-tested.
Comprehensive analysis of testing strategy and coverage across the codebase. Evaluates all test types and identifies gaps.
Professional software QA and code review skill for ensuring code quality, comprehensive test coverage, standards compliance, and security through rigorous testing and validation workflows.
Use for QUICK PR reviews with structured checklists (architecture, patterns, security, performance). Provides step-by-step review process, git diff commands, and review report templates. Best for pull request r...
Use AFTER any code changes (feature implementation, bug fix, refactor) to enforce mandatory dual-pass review. First pass reviews unstaged changes for correctness and convention compliance. Second pass ONLY exec...
Use for QUICK PR reviews with structured checklists (architecture, patterns, security, performance). Provides step-by-step review process, git diff commands, and review report templates. Best for pull request r...
Use when reviewing code changes, pull requests, or performing refactoring analysis with focus on patterns, security, and performance.
Use when the user asks to compare branches, analyze git diffs, review changes between branches, update specifications based on code changes, or analyze what changed. Triggers on keywords like "compare branches"...
Fresheyes provides code review from a larger model. Use when the user asks for fresh eyes.
Rust coding best practices based on Microsoft Pragmatic Rust Guidelines. ALWAYS invoke before writing or modifying Rust code. Covers error handling, API design, performance, and idiomatic patterns.
MANDATORY 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.
Run formatters on files based on the user's conform neovim configuration. Supports multiple languages including JavaScript, TypeScript, Python, Go, Nix, Lua, and more. Use this when the user asks to format, lin...
严格的 Home Assistant 集成代码审查。用于提交 PR 前的全面检查，包括 Quality Scale 规则验证、代码风格、Config Flow、测试覆盖和文档。当用户说"审查我的 HA 集成"、"检查我的代码是否符合 HA 规范"、"帮我 review 一下准...
Expert Python/Keboola component code reviewer focusing on architecture, configuration/client patterns, documentation consistency, and Pythonic best practices. Provides actionable feedback with clear location, p...
TypeScript development with strict mode, Vitest testing, ESLint linting, and CI/CD best practices. Use when working on TypeScript projects, writing tests, configuring linting, or setting up build pipelines.
Automated quality checks and enforcement for code commits. Use when validating code quality, running pre-commit checks, ensuring test coverage, or enforcing coding standards before commits and pushes.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.