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
testing
388

tests-standards

Write focused tests for core user flows and critical paths with clear test names, behavior-focused assertions, mocked external dependencies, and fast execution, deferring edge case testing until explicitly required. Use this skill when creating or modifying test files, writing unit tests, integration tests, or test cases for any feature. Apply when writing test files (test/, __tests__/, spec/, .test.js, .spec.ts, test_*.py), implementing tests for core user workflows, testing critical business logic, mocking external dependencies (databases, APIs, file systems), writing descriptive test names, creating fast-running unit tests, or adding tests at logical completion points of feature development. Use for any task involving test creation, test coverage, test strategy, or test-driven development.

maxritter
maxritter
testing-security
open
code-quality
388

css-standards

Write consistent, maintainable CSS following the project's methodology (Tailwind, BEM, utility classes, CSS modules) with design system adherence and performance optimization. Use this skill when writing or modifying styles, CSS files, utility classes, CSS-in-JS, styled components, or any styling code. Apply when working with .css, .scss, .module.css files, Tailwind utility classes, styled-components, CSS modules, design tokens (colors, spacing, typography), framework-specific styling approaches, optimizing CSS for production, implementing CSS purging or tree-shaking, or avoiding style overrides. Use for any task involving visual styling, layout styling, design system implementation, or CSS organization.

maxritter
maxritter
testing-security
open
testing
388

testing-standards

Prevent common testing anti-patterns that undermine test effectiveness and code quality by ensuring tests verify real behavior rather than mock behavior, keeping production code free from test-only pollution, and enforcing thoughtful mocking strategies. Use this skill when writing or modifying any test files (.test.ts, .test.js, .spec.ts, _test.py, test_*.py, *_test.go, *_spec.rb), when adding mock objects, stubs, spies, or test doubles to test suites, when considering adding methods or properties to production classes that are only called from test code, when setting up complex test fixtures or test data, when tests are failing and you're tempted to adjust mocks to make them pass, when deciding how to isolate code under test from external dependencies, when implementing dependency injection or test seams, during code reviews when reviewing test implementation and mocking strategies, when refactoring tests that have become brittle or hard to maintain, when test setup code is becoming longer than the actual te

maxritter
maxritter
testing-security
open
code-quality
378

validate-openapi-spec

Use when checking if an OpenAPI spec is valid, looking for errors, or running `speakeasy lint`

speakeasy-api
speakeasy-api
testing-security
open
code-quality
376

code-consistency-logging-standards

Check Python logging levels and patterns for correctness. Focus on identifying wrong severity levels and missing exception handling. Use when reviewing code quality.

taylorsatula
taylorsatula
testing-security
open
code-quality
376

investigate-dependencies

Conduct thorough dependency audits to identify redundant code, unused features, and improper usage patterns. Examines each import to ensure we're leveraging existing capabilities rather than reinventing functionality.

taylorsatula
taylorsatula
testing-security
open
testing
376

real-pytest-no-mocks-real-tests

Write pytests that test real public interfaces with actual components, no mocking, and precise assertions. MIRA-specific patterns. Use when creating or reviewing tests.

taylorsatula
taylorsatula
testing-security
open
testing
358

playwright-testing

This skill should be used when user asks about "Playwright", "responsiveness test", "test with playwright", "test login flow", "file upload test", "handle authentication in tests", or "fix flaky tests".

fcakyon
fcakyon
testing-security
open
testing
318

skill-with-frontmatter

A test skill with full YAML frontmatter for testing frontmatter parsing

kasperjunge
kasperjunge
testing-security
open
testing
313

testing-strategy

Use when writing tests, reviewing test code, or discussing testing approach for walkerOS packages. Covers env pattern, dev examples, and package-specific strategies.

elbwalker
elbwalker
testing-security
open
testing
310

go-table-driven-tests

Write Go table-driven tests following Go community best practices and this repository's conventions. Use when writing or refactoring Go tests, especially when you notice repeated test patterns or copy-pasted test code.

Xe
Xe
testing-security
open
code-quality
305

error-messages

Error Message Style Guide for Validation Errors

githubnext
githubnext
testing-security
open
security
305

http-mcp-headers

HTTP MCP Header Secret Support - Implementation Summary

githubnext
githubnext
testing-security
open
testing
304

qa-planning

Generate QA Contract with numbered Gherkin scenarios (G#N) and acceptance criteria (AC#N)

WellApp-ai
WellApp-ai
testing-security
open
testing
304

test-hardening

Convert passed QA Contract criteria to automated tests

WellApp-ai
WellApp-ai
testing-security
open
testing
304

webapp-testing

Test web app UI using Browser MCP and Storybook

WellApp-ai
WellApp-ai
testing-security
open
code-quality
303

writing-nix

Writes idiomatic, performant, and maintainable Nix code. Covers best practices, anti-patterns to avoid (like `with`), module system design, and performance optimization.

khaneliman
khaneliman
testing-security
open
code-quality
303

code-review

Conduct thorough, actionable code reviews focusing on critical issues. Use when reviewing pull requests, analyzing code changes, identifying bugs, security vulnerabilities, or suggesting improvements that developers will actually implement.

khaneliman
khaneliman
testing-security
open
code-quality
303

validating-nix

Validates Nix code correctness, syntax, and buildability. Use when checking for errors, debugging build failures, formatting code, or verifying flake outputs.

khaneliman
khaneliman
testing-security
open
security
303

security-auditing

Comprehensive security vulnerability assessment and configuration review. Use when analyzing code for security flaws, reviewing dependencies for CVEs, auditing access controls, detecting secrets exposure, or validating compliance with security frameworks.

khaneliman
khaneliman
testing-security
open
testing
301

ark-chainsaw-testing

Run and write Ark Chainsaw tests with mock-llm. Use for running tests, debugging failures, or creating new e2e tests.

mckinsey
mckinsey
testing-security
open
security
300

ssrf

服务端请求伪造漏洞检测与利用。当目标存在 URL 参数、远程文件加载、Webhook、PDF 生成、URL 预览功能时使用。

yhy0
yhy0
testing-security
open
security
300

auth-bypass

认证绕过漏洞检测与利用。当目标存在登录功能、权限控制、JWT/Session 认证时使用。包括 IDOR、越权访问等。

yhy0
yhy0
testing-security
open
code-quality
256

coding-guidelines

Use when asking about Rust code style or best practices. Keywords: naming, formatting, comment, clippy, rustfmt, lint, code style, best practice, P.NAM, G.FMT, code review, naming convention, variable naming, function naming, type naming, 命名规范, 代码风格, 格式化, 最佳实践, 代码审查, 怎么命名

ZhangHanDong
ZhangHanDong
testing-security
open
Previous
Page 151 / 389
Next