semgrep
Static analysis and security scanning using Semgrep, a fast, open-source static analysis tool for finding bugs and enforcing code standards. Use when scanning code for security vulnerabilities, code quality iss...
Découvrez les skills tools code quality, comparez leurs dépôts et consultez leurs instructions.
Static analysis and security scanning using Semgrep, a fast, open-source static analysis tool for finding bugs and enforcing code standards. Use when scanning code for security vulnerabilities, code quality iss...
Deep, excruciating code review. Use anytime to analyze code for correctness, edge cases, security, performance, and design issues. Not tied to baseline—this is pure code analysis.
Platform/Language agnostic API delivery and correctness auditor. Use when project contains API endpoints to verify contract alignment, endpoint behavior, and test coverage.
Comprehensive codebase audit for release readiness. Parallel exploration of docs, code, config, tests, and specs to identify cruft, then interactive triage with clear action options.
Apply consistent coding style patterns when writing or reviewing code. Use when generating new code that should follow your established preferences. Works with any language. Complements linters (which handle fo...
This skill should be used when the user asks to "review code", "check for bugs", "audit this file", or wants feedback on code quality, security, and best practices.
Performs structured code reviews focusing on bugs, security, performance, and best practices. Use when reviewing code, pull requests, diffs, or when the user asks for feedback on implementations.
Fix linting and formatting issues automatically
TypeScript, lint, test, and build validation before committing
Review code changes for bugs, logic errors, regressions, and missing tests. Use when the user asks for a code review, review of uncommitted files, or review of specific diffs/files/PR changes. Default to uncomm...
Migrate JavaScript/TypeScript projects from Biome to oxlint + oxfmt with Prettier fallback. Use when user asks to "migrate to oxlint", "switch from biome to oxc", "use oxfmt", or wants to adopt the oxc toolchai...
Performs comprehensive code review with stack detection, deep logic tracing, and double-verification of bugs before reporting
Run comprehensive quality checks including Pint formatting, PHPStan analysis, and Pest tests. Use this before commits, after major changes, or when requested by user.
Verifies code follows Clean Architecture principles in Polibase. Activates when creating or modifying src/domain, src/application, src/infrastructure, or src/interfaces files. Checks dependency rules, entity in...
Criteria for reviewing Codex worker outputs across 5 dimensions. Use when reviewing code submitted by workers before approval.
Review implementation quality and regression risks via claude-delegator (Code Reviewer expert). Use after implementation for complex tasks, refactors, or API changes.
Validate integration impact and regression risks via claude-delegator (Code Reviewer expert). Use for complex tasks or API integration.
Review Claude Code skills for quality and correctness
Genera mensajes de commit descriptivos siguiendo Conventional Commits. Analiza cambios y sugiere mensajes claros. Úsalo cuando escribas commits o menciones "commit".
Run pre-commit checks using src.agents.scripts.pre_commit after editing code. Use when you need automated lint/format hooks on changed files or before running tests and review.
Codex CLI(read-only)を用いて、レビュー→Claude Code修正→再レビュー(ok: true まで)を反復し収束させるレビューゲート。仕様書/SPEC/PRD/要件定義/設計、実装計画(PLANS.md等)の作成・更新直後、major step(>=5 files...
Use when reviewing code, verifying implementations, checking security, validating acceptance criteria, or conducting code reviews for a completed implementation.
Best practices for conducting effective code reviews that improve code quality, share knowledge, and maintain team standards.
Standardized commit message formats and conventions for clear, searchable, and automated-friendly version control history.
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é.