query active

Search Skills

Find the perfect capability for your agent.

Results
53,183
matching skills for this query
Page
2571
of 2660 pages
Keyword
ai
search by name, tag, or description
automation-tools
0

yaml-validator

Comprehensive YAML syntax validation, error fixing, and schema validation for various formats (GitHub Actions, Docker Compose, Kubernetes, GitLab CI). Use when Claude needs to: (1) Validate YAML syntax, (2) Check YAML files for errors, (3) Fix common YAML formatting issues, (4) Validate against schemas like GitHub Actions workflows, Docker Compose files, Kubernetes manifests, or GitLab CI pipelines, (5) Debug YAML parsing errors. Triggers on phrases like "check yaml", "validate yaml", "fix yaml errors", "yaml syntax".

r3mcos3
r3mcos3
tools
open
code-quality
0

code-validator

驗證 maihouses 專案的 TypeScript/React 代碼品質,確保符合 CLAUDE.md 的最高規格標準。當修改或審查代碼時自動使用。

cityfish91159
cityfish91159
testing-security
open
code-quality
0

lint-test-typecheck-policy

Policy สำหรับ enforce code quality ผ่าน linting, testing, และ type checking ใน CI pipeline

AmnadTaowsoam
AmnadTaowsoam
testing-security
open
ide-plugins
0

code-formatter

Format Python code using black, ruff, and isort to ensure consistent style. This skill should be used before committing code to maintain code quality standards and pass CI/CD checks.

omriwen
omriwen
tools
open
code-quality
0

typescript

TypeScript/JavaScript standards for type-safe, maintainable code.

WallysonGalvao
WallysonGalvao
testing-security
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.

arielZusman
arielZusman
tools
open
code-quality
0

baseline-check

Autonomously run quality checks (RuboCop, RSpec) to establish baseline or detect regressions. Triggers before starting development work, after completing changes, when checking code quality, or when explicitly requested. Compares current metrics against previous baseline to identify improvements or regressions in code quality and test coverage.

spiralhouse
spiralhouse
testing-security
open
code-quality
0

sdk-config-validator

Validates Claude Agent SDK configuration files, environment setup, dependencies, and project structure

vanman2024
vanman2024
testing-security
open
automation-tools
0

codereview-style

Review code style, maintainability, and documentation. Checks readability, naming, modularity, abstractions, and documentation accuracy. Use as a final pass on all files.

xinbenlv
xinbenlv
tools
open
code-quality
0

receiving-code-review

Use when receiving code review feedback, processing PR comments, or needing to evaluate suggestions before implementing - requires technical verification not blind agreement

eyadsibai
eyadsibai
testing-security
open
code-quality
0

global-coding-style

Maintain consistent coding style, formatting, and naming conventions across the entire codebase following DRY and YAGNI principles. Use this skill when writing or refactoring any code in any language or framework to ensure consistent indentation, naming patterns, function size, and code organization. Apply this skill when naming variables, functions, classes, or files, when formatting code with proper spacing and line breaks, when removing dead code or unused imports, when extracting duplicated logic into reusable functions, or when ensuring small focused functions that do one thing well. This skill ensures the entire codebase maintains uniform style through automated formatting tools (Prettier, Black, ESLint), follows established naming conventions (camelCase, PascalCase, snake_case), avoids code duplication, removes commented-out code, and prioritizes readability and maintainability over cleverness.

overtimepog
overtimepog
testing-security
open
automation-tools
0

code-analyze

Analyze codebase for patterns, issues, and improvements. Enforces analysis standards while incorporating user-specific requirements.

AEtherlight-ai
AEtherlight-ai
tools
open
ide-plugins
0

coding-guidelines

Comprehensive coding standards for TypeScript/JavaScript projects with React. Use when writing new code, refactoring, or setting up project structure. Focuses on e2e type-safety, readability, and maintainability. Apply to any code creation, file structuring, or technical decision-making tasks.

ramirlm
ramirlm
tools
open
code-quality
0

dependency-auditor

Check dependencies for known vulnerabilities using npm audit, pip-audit, etc. Use when package.json or requirements.txt changes, or before deployments. Alerts on vulnerable dependencies. Triggers on dependency file changes, deployment prep, security mentions.

jonnocraig
jonnocraig
testing-security
open
code-quality
0

feature-doc-review

Review a feature/component documentation to check that it adheres to repo standards.

JohnLudlow
JohnLudlow
testing-security
open
code-quality
0

validate-project

Run full CI validation for the current project directory

jrmatherly
jrmatherly
testing-security
open
code-quality
0

payoo-ios-code-review

Comprehensive iOS code review for Payoo Merchant app. Checks Clean Architecture patterns, MVVM with RxSwift, memory management, Swinject DI, session error handling, layer separation, naming conventions, and SwiftLint compliance. Use when "review code", "check code", "code review", "review PR", "check pull request", or analyzing Swift files in this project.

daispacy
daispacy
testing-security
open
automation-tools
0

general-codereview

Perform thorough code reviews following Google's 5-step methodology. Use when reviewing pull requests, change lists, or any code changes to ensure quality, correctness, and maintainability.

xinbenlv
xinbenlv
tools
open
code-quality
0

enforcing-python-dunders

Ensure Python classes include appropriate, developer-friendly dunder methods—especially __repr__ and __str__. Use when: (1) Writing or modifying Python class definitions in .py files, (2) Refactoring existing Python classes, (3) Adding or improving __repr__, __str__, or natural arithmetic/comparison/container dunders. Do NOT use for: tests, fixtures, mocks, stubs, non-Python files (YAML, JSON, TOML), auto-generated code vendor libraries, or when user explicitly asks not to modify dunders. Ignored paths: tests/, *_test.py, test_*.py, .venv/, build/, dist/, migrations/, __init__.py.

austinogilvie
austinogilvie
testing-security
open
code-quality
0

moai-lang-shell

Shell scripting best practices with bats-core 1.11, shellcheck 0.10, and POSIX compliance.

kivo360
kivo360
testing-security
open
Previous
Page 2571 / 2660
Next