home/categories/testing-security
domain cluster

Testing & Security

QA, penetration testing, and code quality.

9326 اسکلزall categories
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
code-quality
2

comment-analyzer

Use when asked to review code comments for accuracy/quality or explicitly asked to run the comment-analyzer subagent.

troykelly
troykelly
testing-security
open
code-quality
2

design-tokens-validator

[Design System] Validate that code and styles use official design tokens instead of hard-coded values. Use when (1) reviewing CSS/SCSS/Tailwind/styled-components for hard-coded colors/spacing, (2) checking SwiftUI/UIKit for raw color/font values, (3) auditing Unity styles for magic numbers, (4) enforcing design system compliance, (5) user asks to 'check design tokens', 'validate tokens', 'find hard-coded values', or 'audit design system usage'.

CANTAGESTUDIO
CANTAGESTUDIO
testing-security
open
code-quality
2

commit

Validate code with lints and tests, then commit and push

ahtavarasmus
ahtavarasmus
testing-security
open
code-quality
2

refactoring

Linter-driven refactoring patterns to reduce complexity and improve code quality. Use when linter fails with complexity issues (cyclomatic, cognitive, maintainability) or when code feels hard to read/maintain. Applies storifying, type extraction, and function extraction patterns.

buzzdan
buzzdan
testing-security
open
code-quality
2

basedpyright-type-checking

Basedpyright static type checker configuration, installation, and usage patterns. Use when implementing type checking, configuring LSP, comparing type checkers, or setting up strict type validation in Python projects. Triggered by: basedpyright, pyright, type checking, LSP, mypy alternative, static analysis.

laurigates
laurigates
testing-security
open
code-quality
2

code-review

Guide for conducting thorough code reviews focusing on correctness, security, performance, maintainability, and best practices

vinnie357
vinnie357
testing-security
open
code-quality
2

code-metrics-analyzer

Calculate code quality metrics - complexity, coverage, maintainability

paleoterra
paleoterra
testing-security
open
code-quality
2

verification-stack

Use when running verification pipelines, checking test/lint/type status, or ensuring code quality gates pass before completing work

JoshuaOliphant
JoshuaOliphant
testing-security
open
code-quality
2

docusaurus-config

Use when working with docusaurus.config.js/ts files to validate or modify Docusaurus configuration

mcclowes
mcclowes
testing-security
open
code-quality
2

markdown-validation

Validate markdown documentation files for formatting issues, syntax errors, broken links, and quality standards. Use when checking .md files for compliance with documentation standards or after editing markdown files.

auldsyababua
auldsyababua
testing-security
open
code-quality
2

privacy-guard

Enforces zero-tolerance scanning for PII, secrets, and unauthorized file types before code processing.

plutowang
plutowang
testing-security
open
code-quality
2

refactoring

Linter-driven refactoring patterns to reduce complexity and improve code quality in React/TypeScript. Use when ESLint fails with SonarJS complexity issues (cognitive, cyclomatic, expression) or when code feels hard to read/maintain. Applies component extraction, hook extraction, and simplification patterns.

buzzdan
buzzdan
testing-security
open
code-quality
2

code-critic

Critical Code Reviewer. Focuses on security, performance (Big O), and strict typing.

plutowang
plutowang
testing-security
open
code-quality
2

coding-standards

Nature-Spotsプロジェクトのコーディング規約。命名規則、禁止パターン、インポート順序、コメント基準を定義します。コードレビュー時に自動参照されます。

Ryo-cool
Ryo-cool
testing-security
open
code-quality
2

design-consistency

Analyze design system usage, identify inconsistencies across patterns, generate fixes, and maintain visual coherence with automated style guide generation

imsaif
imsaif
testing-security
open
code-quality
2

code-reviewer

Use during verification phase when conducting thorough code reviews and providing constructive feedback based on universal software quality principles.

softleader
softleader
testing-security
open
code-quality
2

coding-standards

PHP coding standards (PSR-12, PHPDoc, type hints) for any PHP project

masanao-ohba
masanao-ohba
testing-security
open
code-quality
2

following-conventions

C++ coding conventions. Use when editing .cpp/.hpp files or asking about C++ style.

tenzir
tenzir
testing-security
open
code-quality
2

pr-comments

Load PR comments and feedback for code review. Use when the user wants to see reviewer feedback, check for unresolved comments, understand what changes are requested, or review discussion on a PR.

rlcurrall
rlcurrall
testing-security
open
code-quality
2

vulture-dead-code

Vulture and deadcode tools for detecting unused Python code (functions, classes, variables, imports). Use when cleaning up codebases, removing unused code, or enforcing code hygiene in CI. Triggered by: vulture, deadcode, dead code detection, unused code, code cleanup, remove unused.

laurigates
laurigates
testing-security
open
code-quality
2

pop-assessment-anthropic

Validates PopKit compliance with Claude Code patterns using concrete standards and automated checks

jrc1883
jrc1883
testing-security
open
code-quality
2

moai-lang-ruby

Ruby 3.4+ best practices with RSpec 4, RuboCop 2, Bundler, and Rails 8 patterns.

AJBcoding
AJBcoding
testing-security
open
code-quality
2

code-quality

Code quality guidelines. ALWAYS use skill for ANY code changes.

motlin
motlin
testing-security
open
Previous
Page 239 / 389
Next