web-design-guidelines
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".
Discover tools code quality skills, compare source repositories and read the instructions for each workflow.
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".
Audit de sécurité du code. Analyse OWASP Top 10, dépendances vulnérables, secrets exposés, et configurations. Utiliser après l'implémentation ou avant une release.
Reviews code changes in the Nick Stack codebase, checking for tech stack patterns, security, type safety, and best practices. Use when reviewing PRs, commits, or code changes.
Comprehensive code review with failure scenario analysis, security checks, and prioritized fix suggestions. Use after /execute to validate implementation quality.
Review code for implementation correctness, scalability, and production readiness. Use when reviewing PRs, auditing code quality, checking for performance issues, or evaluating production readiness. Triggers on...
Reviews code changes for bugs, style issues, and best practices. Use when reviewing PRs or checking code quality.
This 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 d...
Ensure consistent code quality, style, and best practices for mobile apps. Use when writing code, reviewing PRs, or setting up linting.
Check code coverage using Codecov MCP server. Use when user asks to check coverage, find untested code, compare branch coverage, review PR coverage impact, or identify files needing tests. Triggers on phrases l...
Expert-level frontend code review workflow focusing on maintainability, security, performance, and accessibility. Use when reviewing frontend diffs, PRs, components, SPAs, UI logic, or framework-specific code (...
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".
Reviews code changes for bugs, style issues, and best practices. Use when reviewing PRs or checking code quality.
This skill should be used when the user asks to "analyze this project", "what type of project is this", "detect project structure", "understand this codebase", or when Claude needs to determine project type for...
Tools to enforce code cleanliness, reduce technical debt, and maintain architectural standards.
Reduce cyclomatic and cognitive complexity.
Enforces modern TypeScript + Next.js 14+/15 conventions for clean, safe, maintainable code. Invoked by prompt-classifier in IMPLEMENT/EDIT/DEBUG sequences via "clean-code-guardian ". Acts as quality gate before...
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
Security review checklist for code and infrastructure
Activates when user requests architecture analysis, code review, refactoring suggestions, design pattern evaluation, or SOLID principles assessment. Do NOT use for security-specific audits (use security-auditor...
Language-agnostic coding principles for high-quality, maintainable code. Apply when generating new code, reviewing existing code, or refactoring. Covers DRY, KISS, YAGNI, Fail Fast, avoiding over-validation, an...
Code review for all uncommitted changes (staging status is irrelevant). Checks CLAUDE.md compliance, identifies bugs, security issues, style problems, and simplification opportunities.
Review code quality, patterns, and best practices
Apply a production-grade code review checklist for Java backend changes: layering, error handling, security, tests, observability, performance, and maintainability. Use when preparing a PR or reviewing one.
Auto-generate and sync living documentation from code changes
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.