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
11

rspec-testing

This skill should be used when the user asks to "write specs", "create spec", "add RSpec tests", "fix failing spec", or mentions RSpec, describe blocks, it blocks, expect syntax, test doubles, or matchers. Should also be used when editing *_spec.rb files, working in spec/ directory, planning implementation phases that include tests (TDD/RGRC workflow), writing Testing Strategy or Success Criteria sections, discussing unit or integration tests, or reviewing spec output and test failures. Comprehensive RSpec and FactoryBot reference with best practices, ready-to-use patterns, and examples.

hoblin
hoblin
testing-security
open
testing
11

extract-test-failures

Extract and summarize test failures from logs. Use to quickly understand what tests failed and why.

mvillmow
mvillmow
testing-security
open
testing
11

acceptance-criteria-authoring

Write clear, testable acceptance criteria in Given-When-Then format following INVEST principles and BDD best practices.

melodic-software
melodic-software
testing-security
open
testing
11

nuxt-test-skill

A test skill for validating npm-agentskills Nuxt integration

onmax
onmax
testing-security
open
testing
11

security-test-planning

Plan security testing strategies including OWASP testing, penetration test scoping, SAST/DAST integration, and threat-based test case design.

melodic-software
melodic-software
testing-security
open
testing
11

test-helper

Write comprehensive, idiomatic tests following best practices and project conventions. Use this when writing unit tests, integration tests, or test fixtures. Helps ensure proper test structure, mocking, assertions, and coverage.

kcaldas
kcaldas
testing-security
open
testing
11

phase-test-tdd

Generate test files and coordinate test-driven development (TDD). Use when creating tests before implementation or during test phase.

mvillmow
mvillmow
testing-security
open
testing
11

test-spec

Generates comprehensive test specification with unit tests, UI tests, accessibility testing, and beta testing plan. Creates TEST_SPEC.md from PRD and implementation specs. Use when creating QA strategy.

rshankras
rshankras
testing-security
open
testing
11

playwright-dotnet

Guide for E2E testing with Playwright for .NET using Microsoft.Playwright.MSTest.v4 integration

NotMyself
NotMyself
testing-security
open
testing
11

writeunittest

Créer ou mettre à jour un fichier de test unitaire Vitest pour une fonction TypeScript donnée, namespacée via @scripts (namespace.function), en respectant les conventions de test du projet (ExpectType strict, compatibilité pipe, pas de helpers partagés).

duplojs
duplojs
testing-security
open
testing
11

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first

cipherstash
cipherstash
testing-security
open
testing
11

mstest-testing-platform

Guide for using MSTest with Microsoft.Testing.Platform (the new test runner, not legacy VSTest) in .NET 10 projects

NotMyself
NotMyself
testing-security
open
testing
11

test-data-strategy

Plan comprehensive test data management including synthetic data generation, data anonymization, versioning, and environment-specific strategies.

melodic-software
melodic-software
testing-security
open
testing
11

android-testing

Comprehensive testing strategy involving Unit, Integration, Hilt, and Screenshot tests.

new-silvermoon
new-silvermoon
testing-security
open
testing
11

bug-repro-plan

Create a minimal, repeatable reproduction plan for a bug. Use when a junior developer needs clear steps to reproduce and capture evidence.

proflead
proflead
testing-security
open
testing
11

test-pattern-analysis

Analyze existing tests to identify patterns, fixtures, and conventions before writing new tests

mehdic
mehdic
testing-security
open
security
10

gitlab-stack-secrets-manager

Manages Docker secrets for GitLab stack projects, ensuring secrets are never in .env or docker-compose.yml, properly stored in ./secrets directory, and securely integrated with Docker secrets. Use when users need to create secrets, migrate from environment variables, validate secret configuration, audit secret usage, or ensure secrets are never committed to git.

rknall
rknall
testing-security
open
code-quality
10

documentation-structure-validator

Validate documentation structure, check for missing sections, verify markdown syntax, ensure consistency with templates. Use when user mentions docs validation, structure check, README review, documentation quality, or wants to verify documentation completeness.

mverab
mverab
testing-security
open
code-quality
10

project-alignment

PROJECT.md alignment patterns and validation strategies

akaszubski
akaszubski
testing-security
open
code-quality
10

python-standards

Python code quality standards (PEP 8, type hints, docstrings). Use when writing Python code.

akaszubski
akaszubski
testing-security
open
code-quality
10

cross-reference-validation

Validates all documentation references - file paths, links, line numbers, code examples

akaszubski
akaszubski
testing-security
open
code-quality
10

coding-standards-enforcer

Enforce repository coding standards for Swift 6.2 concurrency, Swift language rules. Use when reviewing or implementing Swift code changes.

tomkrikorian
tomkrikorian
testing-security
open
code-quality
10

jbct-review

Thorough parallel JBCT code review. Launches 10 focused reviewers plus aggregator for comprehensive compliance checking.

siy
siy
testing-security
open
code-quality
10

validate

Run validation checks - determines whether to use fast (validate) or full (validate:full) based on changed files

gricha
gricha
testing-security
open
Previous
Page 198 / 389
Next