code-quality
1
code-review
Reviews code for quality, security, and maintainability. Use after implementing features, completing significant work, or when user asks for code review.
jcdoll
testing-security
запрос активен
Поиск skills
Найдите подходящую возможность для вашего агента.
Популярные запросы
Результаты
53,183
skills, соответствующие запросу
Страница
2081
из 2660
Запрос
ai
ищите по названию, тегу или описанию
code-quality
1
vanilla-rails-models
Use when writing Rails models - enforces state-as-records not booleans, concerns as adjectives namespaced under model, invocation ordering, and private indentation
ZempTime
testing-security
ide-plugins
1
review-maintainability
Audit code for DRY violations, dead code, complexity, and consistency issues. Read-only analysis with actionable recommendations. Use before PR or for code quality review. Triggers: review maintainability, code quality, DRY, refactor review.
doodledood
tools
code-quality
1
skill-validator
Validates skills against production-level criteria with 9-category scoring. This skill should be used when reviewing, auditing, or improving skills to ensure quality standards. Evaluates structure, content, user interaction, documentation, domain standards, technical robustness, maintainability, zero-shot implementation, and reusability. Returns actionable validation report with scores and improvement recommendations.
Ameen-Alam
testing-security
code-quality
1
global-coding-style
Write clean, consistent code following project-wide coding style conventions and formatting standards. Use this skill when writing any code in any language or file type throughout the project. Use this skill when naming variables, functions, classes, or files. Use this skill when organizing code structure and indentation. Use this skill when creating functions and deciding function size and scope. Use this skill when removing dead code, unused imports, or commented-out blocks. Use this skill when applying DRY principles to avoid code duplication. Use this skill when ensuring consistent formatting and style across the codebase. Use this skill when refactoring code for better readability and maintainability.
TorbenMerrald
testing-security
automation-tools
1
clean-code
Analyze and improve code quality, readability, and maintainability
pluginagentmarketplace
tools
code-quality
1
dhh-rails-reviewer
Use this agent when you need a brutally honest Rails code review from the perspective of David Heinemeier Hansson. This agent excels at identifying anti-patterns, JavaScript framework contamination in Rails codebases, and violations of Rails conventions. Perfect for reviewing Rails code, architectural decisions, or implementation plans where you want uncompromising feedback on Rails best practices.\n\n<example>\nContext: The user wants to review a recently implemented Rails feature for adherence to Rails conventions.\nuser: "I just implemented a new user authentication system using JWT tokens and a separate API layer"\nassistant: "I'll use the DHH Rails reviewer agent to evaluate this implementation"\n<commentary>\nSince the user has implemented authentication with patterns that might be influenced by JavaScript frameworks (JWT, separate API layer), the dhh-rails-reviewer agent should analyze this critically.\n</commentary>\n</example>\n\n<example>\nContext: The user is planning a new Rails feature and wants
i3ringit
testing-security
code-quality
1
code-review
Review code changes and remove AI-generated patterns like excessive comments, gratuitous defensive checks, type escape hatches, etc.
wtfleming
testing-security
code-quality
1
implementation-safety
Production-ready safety checklists for Rails implementation. Covers nil safety, ActiveRecord patterns, security vulnerabilities, error handling, and performance. Use before marking any file complete during implementation phases.
Kaakati
testing-security
ide-plugins
1
radflow-compliance
Audit and fix AI-generated or existing code for RadOS design compliance. Use after generating UI code or when reviewing PRs. Catches common mistakes like wrong shadows, hardcoded colors, missing components, and incorrect radius hierarchy.
Radiants-DAO
tools
debugging
1
code-review
Perform thorough code reviews with security, performance, and maintainability analysis. Use when user asks to review code, check for bugs, or audit a codebase.
jihe520
tools
code-quality
1
ruby-community-style
Use this skill when writing Ruby code following the RuboCop Community Ruby Style Guide. Provides comprehensive guidance on idiomatic Ruby patterns, method design, class structure, collections, strings, exceptions, and testing. Covers Sandi Metz rules, duck typing, metaprogramming guidelines, and RuboCop enforcement. Appropriate for any task involving .rb files, Ruby code reviews, refactoring, Rails development, or implementing Ruby best practices.
nhlongnguyen
testing-security
automation-tools
1
eval-review
Review LLM-generated diff classifications for the diffview eval system. Use when the user invokes this skill or pastes yanked case data from evalreview (containing "# Diff Classification Review" header). Evaluates whether classifications accurately help code reviewers, provides pass/fail verdict with detailed critique.
fwojciec
tools
code-quality
1
review-readability
Readability-focused code review. Checks for clarity, naming, documentation, and maintainability.
jmreidy
testing-security
automation-tools
1
rule-auditor
Validates code against currently loaded rules and reports compliance violations. Supports auto-fixing violations with confirmation, dry-run mode, and automatic backups. Use after implementing features, during code review, or to ensure coding standards are followed. Provides actionable feedback with line-by-line issues and suggested fixes.
oimiragieo
tools
code-quality
1
typescript
Use when writing TypeScript code. Applies TypeScript best practices for type safety, generics, JSDoc patterns, and maintainable typed code.
sreejithraman
testing-security
code-quality
1
agent-native-reviewer
Use this agent when reviewing code to ensure features are agent-native - that any action a user can take, an agent can also take, and anything a user can see, an agent can see. This enforces the principle that agents should have parity with users in capability and context. <example>Context: The user added a new feature to their application.\nuser: "I just implemented a new email filtering feature"\nassistant: "I'll use the agent-native-reviewer to verify this feature is accessible to agents"\n<commentary>New features need agent-native review to ensure agents can also filter emails, not just humans through UI.</commentary></example><example>Context: The user created a new UI workflow.\nuser: "I added a multi-step wizard for creating reports"\nassistant: "Let me check if this workflow is agent-native using the agent-native-reviewer"\n<commentary>UI workflows often miss agent accessibility - the reviewer checks for API/tool equivalents.</commentary></example>
i3ringit
testing-security