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

490

phase-8-review

Verify codebase quality — architecture consistency, convention compliance, gap analysis. Triggers: code review, architecture check, quality, gap analysis, 코드 리뷰, 품질 검증.

popup-studio-ai

testing-security

open

testing

490

qa-phase

QA Phase execution — L1-L5 test planning, generation, execution, and reporting. Triggers: qa phase, QA test, qa run, QA 실행, QAフェーズ, QA阶段, fase QA, phase QA, QA-Phase, fase QA.

popup-studio-ai

testing-security

open

testing

489

Use when writing, editing, reviewing, or running Helm chart tests for the Astronomer APC repository. Covers pytest patterns, render_chart() usage, sub-chart value nesting, parametrized tests, uv run commands, schema validation, and test organization.

astronomer

testing-security

open

code-quality

487

api-quality-checks

API class validation rules for Scopy plugins. Auto-loads when reviewing or editing `*_api.h` / `*_api.cpp` files or running API quality checks.

analogdevicesinc

testing-security

open

code-quality

487

scopy-doc-format

RST documentation conventions for Scopy plugins including heading styles, toctree syntax, image placeholders, and attribute table format. Auto-loads when writing RST documentation for Scopy plugins.

analogdevicesinc

testing-security

open

code-quality

487

test-automation-quality-checks

JS automated test validation rules for Scopy plugins. Auto-loads when reviewing or writing test automation scripts in `js/testAutomations/`.

analogdevicesinc

testing-security

open

testing

487

scopy-test-format

Test case conventions for Scopy plugins including UID format, RBP priorities, RST test entry templates, and standard test sequences. Auto-loads when writing test case documentation or automated test scripts.

analogdevicesinc

testing-security

open

code-quality

486

design

Generates and maintains a design manifest for visual consistency. In existing projects, reads current styles and documents the design language. In new projects, asks a few questions and generates a starter manifest. The post-edit hook reads the manifest and flags deviations.

SethGammon

testing-security

open

code-quality

486

improve

Autonomous quality improvement loop. Scores a target against a rubric, selects the highest-leverage axis, attacks it, verifies, documents, and loops. No pre-planning between iterations — each loop re-scores from scratch.

SethGammon

testing-security

open

code-quality

486

pr-watch

Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.

SethGammon

testing-security

open

code-quality

486

review

5-pass structured code review — correctness, security, performance, readability, consistency

SethGammon

testing-security

open

testing

486

qa

Browser-based QA verification. Launches a real browser, navigates the app, clicks buttons, fills forms, and tests user flows. Works as a standalone skill or as a phase end condition in campaigns. Requires Playwright (optional dependency, graceful skip if not installed).

SethGammon

testing-security

open

testing

486

setup

First-run experience for the harness. Three modes: Recommended (guided, ~3 min), Full Tour (guided + skill walkthrough, ~8 min), and Express (zero questions, ~30 sec). Installs hooks first, detects stack, configures harness.json, runs a live demo on real code, and prints a reference card.

SethGammon

testing-security

open

testing

486

test-gen

Generate and verify tests — happy path, edge cases, error paths — using the project's own framework and patterns

SethGammon

testing-security

open

testing

486

testing-patterns

Writes Minitest tests with fixtures following 37signals conventions. Uses Minitest (not RSpec) and fixtures (not factories). Use when writing tests, adding test coverage, or creating fixtures. WHEN NOT: For RSpec or FactoryBot patterns (this project uses Minitest + fixtures exclusively). For test configuration/CI setup (see project docs).

ThibautBaissac

testing-security

open

testing

483

azure-app-testing

Expert knowledge for Azure App Testing development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using Azure Load Testing with VNets/private endpoints, JMeter/Locust/Playwright, CI/CD pipelines, or Playwright Workspaces, and other Azure App Testing related development tasks. Not for Azure Test Plans (use azure-test-plans), Playwright Workspaces (use azure-playwright-workspaces), Azure DevOps (use azure-devops), Azure App Service (use azure-app-service).

MicrosoftDocs

testing-security

open

testing

483

azure-test-plans

Expert knowledge for Azure Test Plans development including limits & quotas, security, and integrations & coding patterns. Use when configuring test fields, managing test access, or automating suites, runs, and configs via tcm.exe, and other Azure Test Plans related development tasks. Not for Azure DevOps (use azure-devops), Azure Boards (use azure-boards), Azure Pipelines (use azure-pipelines), Azure App Testing (use azure-app-testing).

MicrosoftDocs

testing-security

open

testing

482

testing

Testing conventions using pytest. Use when writing tests, creating fixtures, or running test suites.

meleantonio

testing-security

open

testing

481

dojo-contributing

Contributor workflow for dojoengine/dojo. Use when implementing or reviewing changes in this repository, especially Rust workspace edits, Cairo fixture refreshes, and CI-parity formatting/lint/test checks.

dojoengine

testing-security

open

code-quality

480

cc-update-review

CC アプデ統合の品質ガードレール。Feature Table 追加時に「書いただけ」を検出し、実装案を強制出力。Use when reviewing CC update integration PRs. Do NOT load for: implementation work, standard reviews, setup.