testing
497
run-agmente-codex-e2e
Run Agmente iOS end-to-end tests against a local Codex app-server endpoint, validate Codex thread/turn protocol flow, and perform mandatory cleanup.
rebornix
testing-security
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
testing
495
write-tests
Guide for writing unit tests. Use this when creating tests to verify Python logic.
microsoft
testing-security
testing
493
li-gong-demo
模拟李工（后端工程师）在架构评审、发布流程、跨团队对齐场景下的工作方式与沟通边界。用于团队内部对齐与培训。
agenmod
testing-security
testing
493
test-quality
Write high-quality JUnit 5 tests with AssertJ assertions. Use when user says "add tests", "write tests", "improve test coverage", or when reviewing/creating test classes for Java code.
decebals
testing-security
testing
493
testing
Sounding-first testing patterns for The Boring JavaScript Stack — one test() API, a Sails-centered trial context, worlds under tests/, JSON and Inertia request testing, mail capture, and browser-capable trials only when the browser truly matters. Use this skill when writing, configuring, or debugging tests in a Sails.js + Inertia.js application.
sailscastshq
testing-security
testing
492
ast-introspection
Use Go AST-aware analysis to enumerate symbols, extract signatures, and propose mechanically safe refactors (read-only by default).
pilinux
testing-security
testing
492
config-loader-helper
Diagnose configuration-related failures, enumerate required env vars, and guide safe local test setup (no secrets).
pilinux
testing-security
testing
492
db-infra-mocks
Propose minimal seams and local substitutes so tests run without real RDBMS/Redis/Mongo infrastructure.
pilinux
testing-security
testing
492
fix-suggester
Diagnose failures and propose minimal, test-backed fixes with verification and rollback instructions.
pilinux
testing-security
testing
492
test-runner
Run and triage Go tests with correct environment handling; produce compact, actionable failure summaries.
pilinux
testing-security
testing
491
csharp-tunit
Get best practices for TUnit unit testing, including data-driven tests
foxminchan
testing-security
testing
490
zero-script-qa
Zero Script QA — test without scripts using structured JSON logging and Docker monitoring. Triggers: zero-script-qa, log testing, docker logs, QA, 제로 스크립트 QA.
popup-studio-ai
testing-security
testing
489
chart-tests
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
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
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
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
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
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
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
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
testing
478
pigweed-kernel-testing
Instructions for running tests and lints for the Pigweed kernel (`pw_kernel`).
pigweed-project
testing-security