static-analysis
Run static analysis (linting, type checking) on the codebase.
Découvrez les skills content media code quality, comparez leurs dépôts et consultez leurs instructions.
Run static analysis (linting, type checking) on the codebase.
Run all verification checks (static analysis, test, format).
Rust code quality standards and documentation practices. Use when reviewing Rust code, cleaning up churn, writing docstrings, or following rustdoc conventions.
PRの全フィードバック(CodeQL、Copilotレビュー、手動コメント)を取得し、漏れなく対応する
Review unpushed commits before pushing for code quality, bugs, security issues, and error handling. Use when preparing to push commits, want pre-push code review, or need to validate changes before pushing. Run...
Testing inteligente con generación automática de tests, detección de flaky tests y análisis de cobertura
This skill should be used when the user asks to "optimize dotfiles", "optimize my dotfiles", "improve shell", "improve my shell configuration", "check configs", "check my configuration", "audit dotfiles", "anal...
Use when designing R function APIs, reviewing R code for design issues, writing functions for R packages, or evaluating argument ordering and naming decisions. Does NOT cover: style/linting, error handling (rla...
Process and implement code review feedback systematically. Use when user provides reviewer comments, PR feedback, code review notes, or asks to implement suggestions from reviews.
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform comp...
Enforces secure coding practices. Required after all code implementations to run CodeGuard security check. Covers input validation, secrets management, and OWASP countermeasures.
Use when refactoring, cleaning up, or enhancing the lib-electronic-components codebase. Provides guidance on architecture patterns, known issues, duplication hotspots, and recommended improvements.
Enforced coding standards and best practices for the project, including rules on comments and libraries.
Provide structured software code reviews that confirm scope, focus on root causes, evaluate tests, and enforce project conventions.
Validates React code for Rules of Hooks violations. Catches issues like hooks called after conditional returns that cause production crashes (React error
Comprehensive code review for Ishkul's React Native/TypeScript frontend and Go backend. Checks for quality, security, performance, and adherence to project conventions. Use after implementing features or during...
Use when working with Python code and pyright-lsp plugin is enabled - for finding references, checking types, navigating definitions, or verifying type correctness
Rust 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, t...
Enforce Laravel Best Practices when generating code, reviewing code, and writing tests (SRP, skinny controllers, FormRequests, service/action classes, DRY, Eloquent/Collections, Blade query avoidance, eager loa...
Audits Go code for error handling best practices - proper wrapping with %w, preserved context, meaningful messages, no error swallowing. Use before committing Go code or during error handling reviews.
Sets up Node.js/TypeScript development environment with npm/yarn, dependencies, ESLint, Prettier, testing (Jest/Vitest), and TypeScript type checking. Ensures consistent tooling configuration. Use when starting...
Audits Go code for control flow excellence - early returns, minimal nesting, small blocks. Checks for happy path readability, guard clauses, and refactoring opportunities. Use before committing Go code or durin...
Audits TypeScript code for type safety best practices - no any usage, branded types for IDs, runtime validation, proper type narrowing. Use before committing TypeScript code or during type system reviews.
Review React components using Mantine UI library for accessibility, Styles API correctness, component patterns, and common pitfalls. Use when reviewing Mantine code or before merging Mantine-based PRs.
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é.