Découvrez les skills databases code quality, comparez leurs dépôts et consultez leurs instructions.
SonarLint best practices for Next.js 16 applications. Covers pre-merge quality checks, issue severity prioritization, common fixes for TypeScript/Next.js, and when to defer minor issues. Use when performing cod...
Code review skill. Use when reviewing changes, commits, branches, or pull requests. Focuses on bugs, structure, performance with actionable feedback.
Expertise in reviewing code for style, security, and performance. Use when the user asks for "feedback," a "review," or to "check" their changes.
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
Structural code search and refactoring using comby, a tool for matching and rewriting code based on syntax structure rather than regex. Use when performing code refactoring, renaming patterns across files, find...
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.
Audits code and plans against the 9 Articles of Development and Pre-Implementation Gates. Use this skill before submitting code or when the user asks for a review.
Create commits with code quality checks and conventional commit messages
Expert workflow for refactoring large Rust codebases, modularizing monolithic files, and establishing a robust quality gate using Clippy, formatting, and a comprehensive test suite (unit + integration). Use whe...
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...
Create Pull Requests with pre-flight checks and proper formatting
Validate code compliance with Gemini mod rules (core, modules, features, UI, WebSocket, state)
Run all validations before pushing to remote
Run linting for Lua and TCL code
Technical copy editing and proofreading by a peer Principal Engineer. Reviews writing for correctness, clarity, and style—pointing out issues for you to fix rather than making changes automatically.
Systematically transform codebase from 6.5/10 to 9/10 professional standards through testing, type safety, refactoring, and best practices
Check and fix C code according to 42 School's Norminette standards. Use when checking code style, before committing, or when user mentions norm/norminette.
Use this skill when asked to create a pull request (PR). It ensures all PRs follow the repository's established templates and standards.
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.
Use when reviewing code, PRs, or discussing code quality standards. Applies team coding standards and review methodology.
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é.