debugging
0
testing-anti-patterns
This skill should be used when reviewing test code, the user asks "is this test good", "test quality", "mock properly", or when tests behave unexpectedly. Identifies common testing mistakes.
pproenca
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
ide-plugins
0
ruby-quality
Interpretive guidance for Ruby code quality using RuboCop (configurable) or StandardRB (zero-config). Use when linting Ruby files, configuring Ruby tools, troubleshooting lint errors, or understanding tool selection.
racurry
tools
debugging
0
code-review
Comprehensive code review focusing on quality, security, performance, and best practices. Use when reviewing PRs, commits, or code changes.
gtakairo
tools
automation-tools
0
transformation-verifier
Verifies that code slob that was transformed into clean code does not modify the original behavior of the code. Use when the user asks to verify code by providing you with a directory of the files.
Jazz23
tools
ide-plugins
0
auto-linter-expert
Automatically identifies and fixes linting, formatting, and style violations. Trigger this when a user says "lint", "format", "fix style", or "tidy up".
umaranit
tools
automation-tools
0
naming-reviewer
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
luohaha
tools
ide-plugins
0
coding-supervisor
Plans coding tasks and manages the process of making changes to code.
artificialnatures
tools
ide-plugins
0
js-quality
Interpretive guidance for JavaScript/TypeScript code quality using biome (modern) or eslint+prettier (traditional). Use when linting JS/TS files, configuring JS/TS tools, troubleshooting lint errors, or understanding tool selection.
racurry
tools
ide-plugins
0
google-shell-style-guide
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.
pproenca
tools
ide-plugins
0
javascript-human-made
Human Made JavaScript coding standards. Apply when writing JavaScript or TypeScript, reviewing JS code, or working on frontend features. Covers ES6+ conventions, modern patterns, and ESLint configuration.
humanmade
tools
debugging
0
detecting-security-vulnerabilities
Scans code for security vulnerabilities and unsafe patterns. Use when the user asks about security, mentions OWASP, credentials, secrets, XSS, SQL injection, or wants to audit code for threats.
WesleySmits
tools
ide-plugins
0
scala-conventions-enforcer
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.
matthew-bram
tools
ide-plugins
0
lint-instructions
Detect and fix violations of project instructions defined in .claude/rules/. Use when checking code compliance, reviewing changes, or when the user asks about instruction violations.
seijikohara
tools
automation-tools
0
project-reviewer
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.
dm-nice
tools
ide-plugins
0
refactoring
Apply refactoring patterns when consolidating code, extracting functions, or discussing DRY principles. Use when identifying duplicate code, planning consolidation, or discussing code organization. Auto-apply when editing files in src/ or when user mentions "duplicate", "refactor", "DRY", "extract", "consolidate", or "similar code".
surfdeeper
tools
ide-plugins
0
planning-refactors
Uses ast-grep to find patterns and analyze code for refactoring. Use when planning refactors, finding deprecated API usage, migrating code, or analyzing code quality before changes. For simple code search, use searching-code instead.
disusered
tools
debugging
0
complexity-check
Analyzes code complexity metrics and identifies areas that are too complex for developers to easily understand
Jacobgokul
tools
ide-plugins
0
bosun-typescript
TypeScript best practices and patterns. Use when writing, reviewing, or debugging TypeScript code. Provides strict typing, ESLint configuration, testing patterns, and framework guidance.
curphey
tools
ide-plugins
0
lsp-enable
Use when navigating code, understanding unfamiliar functions, finding definitions or references, tracing call hierarchies, preparing for refactoring, or analyzing code impact. Enforces LSP-first semantic code intelligence with mandatory pre-edit checks, impact analysis before refactoring, and post-edit diagnostics. Provides IDE-like precision for code operations in large codebases. Covers navigation (goToDefinition, findReferences), understanding (hover, documentSymbol), and call analysis (incomingCalls, outgoingCalls).
zircote
tools
automation-tools
0
review-architecture
Reviews code for compliance with the project's Modular Monolith architecture, strict boundary rules, and coding standards. Use before committing or when reviewing a PR.
hieupvXmasEve
tools