domain cluster

Tools & Utilities

Essential command-line tools and system utilities.

32082 skillsall categories
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
ide-plugins
0

code-quality

Fix lint errors, format code, run type checking, check code quality. Use when fixing linting issues, formatting Python, running ruff, running ty, checking TypeScript types, or ensuring code quality.

mpolatcan
mpolatcan
tools
open
ide-plugins
0

code-quality

Run code quality checks (ruff, mypy, pytest) and optionally simplify code. This skill should be used when the user wants to check code quality, run linters, run tests, or simplify recently modified code. Triggered by /lint, /check, or /code-quality commands.

s-hiraoku
s-hiraoku
tools
open
ide-plugins
0

typescript-expert

Expert guidance for writing TypeScript code following modern best practices, targeting TypeScript 5.x and ES2022. Use this skill when writing, reviewing, or refactoring TypeScript code in any .ts or .tsx file. Provides comprehensive guidelines on type system usage, architecture patterns, security, testing, and performance.

edneyreis999
edneyreis999
tools
open
ide-plugins
0

global-coding-style

Apply consistent coding style and formatting standards using automated tools (ESLint, Prettier, Ruff) with clear naming conventions, top-down code organization, and appropriate function/component sizing. Use this skill when writing any code in any language, naming files and variables, structuring code within files, organizing imports, configuring linters and formatters, or setting up pre-commit hooks. Apply when working on TypeScript/JavaScript files, Python files, .NET/C# files, configuration files (tsconfig.json, .prettierrc, .eslintrc), or any code that needs consistent formatting and naming. This skill ensures automated formatting with Prettier/Ruff (let tools handle it), ESLint/analyzer enforcement, TypeScript strict mode always enabled, proper naming conventions (PascalCase.tsx for React components, camelCase.ts for utilities, IPascalCase for interfaces with I prefix, PascalCase for types without prefix, camelCase for functions/constants/database fields/API endpoints/JSON keys, no underscore prefix for

TheophilusChinomona
TheophilusChinomona
tools
open
ide-plugins
0

cursor-rules-writing

Create Cursor IDE rules in .mdc format with proper frontmatter, glob patterns, and cross-references. Covers rule structure, file organization, triggering mechanisms, and quality standards. Use when creating or modifying Cursor rules for context injection.

meriley
meriley
tools
open
ide-plugins
0

lint-and-validate

Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, types, static analysis.

seanpham99
seanpham99
tools
open
automation-tools
0

security-check

Protects critical files and detects hardcoded secrets before risky edits. Use when "security check", "audit my settings", "check for secrets", before editing .zshrc or config files.

Eddale
Eddale
tools
open
ide-plugins
0

forge-lang-typescript

TypeScript development standards including type checking, jest/vitest, eslint, and prettier. Use when working with TypeScript files, tsconfig.json, or .ts/.tsx files.

martimramos
martimramos
tools
open
ide-plugins
0

haskell-programming-reviewer

Expertise in reviewing Haskell codebases using modern functional programming idioms. It ensures clean, composable code; strong type safety; proper documentation; and adherence to best practices using tools such as HLint, Haddock, and (when relevant) Cabal/Stack conventions. Use when the user asks for "feedback," a "review," or to "check" their changes.

frankhjung
frankhjung
tools
open
debugging
0

bun-testing

Testing guidelines for Bun/TypeScript projects using bun:test framework. Use when writing tests, creating test files, debugging test failures, setting up mocks, or reviewing test code. Triggers on *.test.ts files, test-related questions, mocking patterns, and coverage discussions.

SlavaMelanko
SlavaMelanko
tools
open
debugging
0

gdscript-quality-checker

Analyze GDScript code for quality, best practices, anti-patterns, and refactoring opportunities. Use this when the user wants to review code quality, check for Godot-specific issues, or improve code maintainability.

cautiouskurns
cautiouskurns
tools
open
ide-plugins
0

file-suggestion

Set up fast file suggestions for Claude Code using ripgrep, jq, and fzf. Use this skill when users want to improve file autocomplete performance or add custom file suggestion behavior.

RBozydar
RBozydar
tools
open
automation-tools
0

validator

Runs local validation operations for any project. Auto-detects language/framework and runs linting, type checking, tests, and dead code detection. Use this when the user says "validate", "run validation", "check code", "lint and test", or "run checks".

neonwatty
neonwatty
tools
open
ide-plugins
0

python-quality

Interpretive guidance for Python code quality using ruff (modern) or pylint+isort+black (traditional). Use when linting Python files, configuring Python tools, troubleshooting lint errors, or understanding tool selection.

racurry
racurry
tools
open
ide-plugins
0

reviewing-code-quality

Automated tooling and detection patterns for JavaScript/TypeScript code quality review

djankies
djankies
tools
open
ide-plugins
0

specforge

Auto-invoked capability for language specifications, coding standards, and best practices. Activates when writing code to ensure correctness.

krisarmstrong
krisarmstrong
tools
open
ide-plugins
0

enforcing-code-linting

Runs ESLint, Prettier, and stylelint against changed files and suggests or applies fixes. Use when the user mentions linting, code style, PR review, formatting issues, or wants to check code quality before committing.

WesleySmits
WesleySmits
tools
open
automation-tools
0

security-scanning

Security scanning patterns using gitleaks, PII detection, and secret scanning. Use when writing scripts that handle sensitive data, committing code, or setting up security automation. Includes gitleaks configuration, custom PII rules, and pre-commit hooks.

aculich
aculich
tools
open
debugging
0

simplecov

Comprehensive test coverage analysis and improvement for Ruby and Rails applications using SimpleCov and SimpleCov Console formatter. Automatically runs coverage reports, identifies gaps, suggests tests, and enforces coverage standards. Integrates with RubyCritic for holistic code quality. Use when running tests, analyzing coverage, improving test suites, or setting up coverage tracking in Ruby/Rails projects.

el-feo
el-feo
tools
open
automation-tools
0

test-suggester

Proactively suggests tests when code changes are detected. Activates when functions are created, logic is modified, security-sensitive code is added, or bug fixes are implemented. Provides non-intrusive test recommendations to help vibe coders ship with confidence.

devtunehq
devtunehq
tools
open
debugging
0

explore

Systematically explore a codebase area and find/fix obvious issues with fresh eyes.

ianwatts22
ianwatts22
tools
open
ide-plugins
0

ast-grep

Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for code patterns, find specific language constructs, or locate code with particular structural characteristics.

erwinkn
erwinkn
tools
open
ide-plugins
0

pythonista-reviewing

Code review best practices for Python projects. Use when reviewing code, PRs, or diffs. Triggers on "review", "code review", "PR", "pull request", "diff", "check this", "look at this code", "quality", "refactor", or when examining code for issues.

gigaverse-app
gigaverse-app
tools
open
Previous
Page 1205 / 1337
Next