debugging
1
code-review
Code review mode - comprehensive review with security, performance, and maintainability focus
thoreinstein
tools
domain cluster
Tools & Utilities
Essential command-line tools and system utilities.
32082 مهارةall categories
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
automation-tools
1
refactoring-test-suites
Enforces consistent test quality, structure, and maintainability across any programming language by applying project-wide conventions for test naming, structure, parameterization, and classification. Use for messy test suites, inconsistent naming, improving CI alignment and developer readability, or when the user mentions test cleanup, test organization, or test standardization.
kynoptic
tools
ide-plugins
1
rust-pragmatist
Automatically review Rust code after edits to .rs files, providing pragmatic suggestions for idiomatic patterns, performance, safety, and code organization. Activate when Rust source files are modified or when explicitly requested.
ccustine
tools
debugging
1
performance-fundamentals
Auto-invoke when reviewing loops, data fetching, rendering, database queries, or resource-intensive operations. Identifies N+1 queries, unnecessary re-renders, memory leaks, and scalability issues.
DanielPodolsky
tools
debugging
1
security-review
Identify security vulnerabilities, performance issues, and code quality problems through systematic analysis adapted to project's technology stack and domain. Use when reviewing code, assessing security, auditing. Triggers: 'security', 'vulnerability', 'audit', 'review', 'OWASP', 'injection', 'authentication', 'authorization', 'XSS', 'CSRF', 'secure', '보안', '취약점', '검토', '리뷰', '감사', '인증', '인가', '보안검사'.
vanillacake369
tools
ide-plugins
1
fundamentals-gate
Verify code quality standards are met - naming, structure, DRY principles. Issues result in SUGGESTIONS for improvement.
DanielPodolsky
tools
ide-plugins
1
code-quality-tools
Automated code quality fixes for linting, types, unused variables, and error handling; use when fixing code quality issues in bulk
antoineschaller
tools
debugging
1
codebase-analysis
Analyze codebase for existing implementations, test coverage, and code patterns. Use when checking what's already implemented, finding related code, or assessing test coverage for features.
pkuppens
tools
automation-tools
1
technical-feedback
Use when receiving or giving code review feedback, implementing review suggestions, addressing PR comments, or evaluating technical suggestions. Covers both directions - receiving feedback (verify before implementing, push back on principle violations) and giving feedback (prioritize project principles, actionable critique). Triggers on review, feedback, suggestions, PR comments, implement this, fix this, address comments.
krwhynot
tools
ide-plugins
1
markdown-compliance
Strict guidelines and enforcement of markdownlint rules. Use this skill to ensure all generated markdown files are syntactically correct and render flawlessly across platforms.
kurokeita
tools
automation-tools
1
static-analysis
Perform automated static code analysis on modified files. Triggers automatically after code changes to catch common issues before QA Lead review. Checks for: code complexity, dead code, type errors, import issues, and style violations. Use when: - Code files have been modified - Before committing changes - As pre-check for QA Lead review - User asks "analyze this code" or "check for issues" This skill runs lightweight static analysis tools (pylint, mypy, ruff for Python; eslint, tsc for TypeScript) and reports findings in structured format.
johannesfritz
tools
automation-tools
1
security-review
This skill should be used when the user asks to "security review", "check for vulnerabilities", "audit security", "find security issues", "security scan", "check for injection", "find hardcoded secrets", "OWASP check", or mentions reviewing code specifically for security concerns.
JesseNaranjo
tools
automation-tools
1
global-coding-style
Apply consistent coding style, naming conventions, and code formatting across the NestJS API codebase. Use this skill when writing any TypeScript code in the apps/api/ or packages/shared/ directories, when naming variables, functions, classes, or files, when structuring imports and exports, or when following the project's ESLint and Prettier configurations. This includes enforcing strict TypeScript settings (no any, prefer-nullish-coalescing, prefer-optional-chain), using proper file naming patterns (kebab-case for files, PascalCase for classes), organizing imports alphabetically, and maintaining 120 character line width. Apply when writing any *.ts file, refactoring code, or reviewing code quality.
imkdw
tools
ide-plugins
1
eslint-fix
TypeScript/ESLint error fix guide, helps AI quickly locate and fix common lint errors, prioritizing auto-fix commands for formatting issues.
TrueNine
tools
debugging
1
ui-ux-a11y-static-review
This skill should be used when performing static UI/UX and accessibility reviews of frontend codebases and producing a three-step report (context mapping, violations, executive synthesis) from code only.
prof-ramos
tools
automation-tools
1
code-refactor-analyzer
Analyzes codebase for refactoring needs, generates todo reports, and validates completion
chaorenex1
tools
ide-plugins
1
pattern-extraction
Detect and extract patterns from codebases for template generation
Lobbi-Docs
tools
ide-plugins
1
rubycritic
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.
el-feo
tools
automation-tools
1
code-fixer
Senior Code Fixer to apply fixes based on reviews. ONLY activates on explicit user request.
islammesabah
tools