আপনার এজেন্টের জন্য উপযুক্ত সক্ষমতা খুঁজে নিন।
Comprehensive iOS SDK code review for Payoo iOS Frameworks. Checks Clean Architecture patterns, MVVM implementation, UseCase patterns, memory management, naming conventions, API design, and Swift best practices. Use when "review code", "check code", "code review", "review PR", or analyzing Swift files in this project.
Comprehensive Ruby and Rails code review using Sandi Metz rules and SOLID principles. Automatically runs rubycritic and simplecov, analyzes changed files in current branch vs base branch, identifies OOP violations, Rails anti-patterns, security issues, and test coverage gaps. Outputs REVIEW.md with VSCode-compatible file links. Use when reviewing Ruby/Rails code, conducting code reviews, checking for design issues, or when user mentions code review, pull request review, or code quality analysis.
Activates when reviewing code to identify quality issues, security vulnerabilities, and suggest improvements
Analyzes code for complexity issues. Use when code feels hard to understand, reviewing maintainability, or planning refactoring.
Integrate RubyCritic to analyze Ruby code quality and maintain high standards throughout development. Use when working on Ruby projects to check code smells, complexity, and duplication. Triggers include creating/editing Ruby files, refactoring code, reviewing code quality, or when user requests code analysis or quality checks.
Enforces TypeScript strict mode compliance, eliminates any types, ensures type safety, and maintains strict linting standards. Use when TypeScript errors occur, any types need elimination, or strict mode compliance is required.
Comprehensive code review focusing on quality, security, performance, and best practices. Use when reviewing PRs, commits, or code changes.
Follow core coding style principles including SOLID, DRY, KISS, and YAGNI when writing code. Apply consistent naming conventions, meaningful variable names, small focused functions, automated formatting, and proper code organization. Use this skill across all programming languages and file types when writing or refactoring code. Use when creating functions, classes, modules, or components to ensure Single Responsibility Principle, when avoiding code duplication (DRY), when choosing simple over clever implementations (KISS), or when resisting premature optimization and speculative features (YAGNI). Use when establishing naming conventions, removing dead code, or maintaining consistent indentation and formatting. Apply these principles universally across backend (.ts, .js, .py, .java, .go), frontend (.tsx, .jsx, .vue), and configuration files.
Automatically monitor, evaluate, and resolve CodeRabbit and Qodo PR review comments. Waits for review bots to comment, evaluates suggestions intelligently, applies fixes, and marks comments as resolved. Designed to run in ralph-loop for continuous operation. Triggers: "resolve PR comments", "fix review issues", "handle coderabbit", "address qodo feedback", "PR review loop", "/pr-resolve"
Validate file placement against canonical structure rules and auto-fix violations. Use before committing or when validating project structure.
Audit and fix accessibility issues for WCAG 2.1 AA compliance. Use when reviewing UI components, implementing forms, building modals, or before releases.
Expert code naming review and refactoring. Reviews variables, functions, and classes to improve readability and maintainability using master-level naming principles. Use when: (1) User asks to review naming/variable names in code, (2) User wants to improve code readability, (3) User requests naming suggestions or refactoring, (4) User mentions code quality or maintainability concerns related to naming, (5) User asks to apply best practices to naming
Distill a failure into a reusable principle and preflight check.
This skill should be used when the user asks to "refactor shell script", "fix bash style", "review shell code", "apply Google style guide", "improve shell script", mentions "shellcheck", or discusses bash/shell coding standards and best practices.
License checking and compatibility. Use when evaluating dependency licenses.
This skill should be used proactively before writing any Scala code for the first time in a session. It ensures all Scala code adheres to project-specific coding standards, formatting rules, naming conventions, and architectural patterns defined in the comprehensive style guide. Trigger this skill when about to write Scala classes, traits, objects, or modify existing Scala files.
Scan entire Python project directories and review all .py files for Clean Code principles. Use when the user requests project-wide code review with /review-project command, wants to analyze multiple files, or needs to identify which files need refactoring most. Requires MCP tools list_directory and read_file.
