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
1K

reviewing-openmc-code

Reviews code changes in the OpenMC codebase against OpenMC's contribution criteria (correctness, testing, physics soundness, style, design, performance, docs, dependencies). Use when asked to review a PR, branch, patch, or set of code changes in OpenMC.

openmc-dev
openmc-dev
testing-security
open
testing
1K

playwright-e2e

writing, running, and debugging Playwright tests. working with their output from github actions

forcedotcom
forcedotcom
testing-security
open
testing
997

effect-http-testing

Testing Effect HttpApi services end-to-end. Use when writing tests that involve Effect's HttpApi, HttpApiBuilder, HttpClient, HttpServer, or when testing any HTTP service/plugin built with @effect/platform. Covers proper layer composition, test server setup, HttpClient injection, and common pitfalls.

RhysSullivan
RhysSullivan
testing-security
open
code-quality
994

security-scan-diff

Scan for malicious code in git diff between a tag/commit and HEAD

dyoshikawa
dyoshikawa
testing-security
open
security
992

winapp-identity

Enable Windows package identity for desktop apps to access Windows APIs like push notifications, background tasks, share target, and startup tasks. Use when adding Windows notifications, background tasks, or other identity-requiring Windows features to a desktop app.

microsoft
microsoft
testing-security
open
security
992

winapp-signing

Create and manage code signing certificates for Windows apps and MSIX packages. Use when generating a certificate, signing a Windows app or installer, or fixing certificate trust issues.

microsoft
microsoft
testing-security
open
testing
990

analyze-failures

Analyze Playwright E2E test failure reports from CI. Parses merged blob reports, groups similar errors, and delegates to specialized subagents for investigation and fixes. Use when CI tests fail or when asked to fix E2E test failures.

saleor
saleor
testing-security
open
code-quality
987

pre-pr-checklist

Final checks before submitting a pull request. Use when preparing to create a PR, to ensure formatting, linting, and the correct tests have been run.

golemcloud
golemcloud
testing-security
open
security
987

auth-nodejs-cloudbase

CloudBase Node SDK auth guide for server-side identity, user lookup, and custom login tickets. This skill should be used when Node.js code must read caller identity, inspect end users, or bridge an existing user system into CloudBase; not when configuring providers or building client login UI.

TencentCloudBase
TencentCloudBase
testing-security
open
security
987

auth-tool-cloudbase

CloudBase auth provider configuration and login-readiness guide. This skill should be used when users need to inspect, enable, disable, or configure auth providers, publishable-key prerequisites, login methods, SMS/email sender setup, or other provider-side readiness before implementing a client or backend auth flow.

TencentCloudBase
TencentCloudBase
testing-security
open
security
987

auth-web-cloudbase

CloudBase Web Authentication Quick Guide for frontend integration after auth-tool has already been checked. Provides concise and practical Web authentication solutions with multiple login methods and complete user management.

TencentCloudBase
TencentCloudBase
testing-security
open
security
987

auth-wechat-miniprogram

CloudBase WeChat Mini Program native authentication guide. This skill should be used when users need mini program identity handling, OPENID/UNIONID access, or `wx.cloud` auth behavior in projects where login is native and automatic.

TencentCloudBase
TencentCloudBase
testing-security
open
testing
987

debugging-hanging-tests

Diagnosing and fixing hanging worker executor or integration tests. Use when a test hangs indefinitely, times out, or appears stuck during execution.

golemcloud
golemcloud
testing-security
open
testing
987

golem-scala-integration-tests

Run and debug Golem Scala SDK integration tests. Use when running golem-scala integration tests, debugging test failures, or working with GolemExamplesIntegrationSpec.

golemcloud
golemcloud
testing-security
open
testing
987

modifying-test-components

Building or modifying test WASM components in test-components/. Use when a test component needs to be rebuilt, a new test component is needed, or SDK changes require downstream test component rebuilds.

golemcloud
golemcloud
testing-security
open
testing
987

rebuild-all-test-components

Rebuilds all test WASM components from scratch. Use when explicitly asked to rebuild all test components, or when there are merge conflicts in any test-components/*.wasm files.

golemcloud
golemcloud
testing-security
open
testing
987

testing

Running and debugging tests in the Golem workspace. Use when writing tests, running specific tests, filtering tests, debugging test failures, or understanding test infrastructure.

golemcloud
golemcloud
testing-security
open
code-quality
983

basic-syntax

If-else formatting, spacing, function parameters, and conditional rendering rules for the Trezor Suite codebase. Use when writing or reviewing TypeScript/React code.

trezor
trezor
testing-security
open
code-quality
983

comments

Comment formatting conventions for the Trezor Suite codebase. Use when writing or reviewing code comments.

trezor
trezor
testing-security
open
code-quality
983

tests

Test style guidelines including naming conventions, mock organization, translation handling, and file structure. Use when writing or organizing tests in the Trezor Suite codebase.

trezor
trezor
testing-security
open
code-quality
983

typescript

TypeScript-specific conventions including ts-expect-error usage, unknown vs any, const assertions, and type vs interface preferences. Use when writing TypeScript code.

trezor
trezor
testing-security
open
testing
983

common-issues

Known issues and their solutions in the Trezor Suite monorepo. Use when encountering build failures, test failures, or environment problems.

trezor
trezor
testing-security
open
testing
983

defensive-programming

Type safety practices including exhaustive checks, explicit return types, and Result-based error handling. Use when writing TypeScript logic that handles multiple cases or error conditions.

trezor
trezor
testing-security
open
testing
983

tests-commands

Commands for running unit tests in the Trezor Suite monorepo. Use when you need to run tests for specific packages or the entire project.

trezor
trezor
testing-security
open
Previous
Page 114 / 389
Next