اشتہار[ For iPhone / iPad ] 🔥 Nugget کی طرف سے حیرت انگیز انٹرایکٹو وال پیپرز۔ ایسا پہلے کبھی نہیں دیکھا!

skills.homescapability registry تلاش

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

432

eval-quality-workflow

Fix or review a single evaluation against all EVALUATION_CHECKLIST.md standards. Use "fix" mode to refactor an eval into compliance, or "review" mode to assess compliance without making changes. Use when user asks to fix, review, or check an evaluation's quality. Trigger when the user asks you to run the "Fix An Evaluation" or "Review An Evaluation" workflow. Do NOT use for reviewing ALL evals against a single code quality standard (use code-quality-review-all instead).

UKGovernmentBEIS

testing-security

code-quality

432

eval-validity-review

Review a single evaluation's validity — whether its claims hold up, whether its name is accurate, whether samples can be both succeeded and failed at, and whether scoring measures ground truth. Use when user asks to check validity of an eval, or as part of the Master Checklist workflow. Do NOT use for code quality or test coverage (use eval-quality-workflow or ensure-test-coverage instead).

UKGovernmentBEIS

testing-security

testing

432

acir-formal-proofs

Build and run ACIR formal proof tests with SMT verification. Generates ACIR artifacts from noir's ssa_verification tool, then runs each test individually with user-specified time/memory limits, and updates the README results table.

AztecProtocol

testing-security

testing

432

debug-e2e

Interactive debugging for failed e2e tests. Orchestrates the debugging session but delegates log reading to subagents to keep the main conversation clean. Use for ping-pong debugging sessions where you want to form and test hypotheses together with the user.

AztecProtocol

testing-security

testing

432

ci-maintenance-workflow

CI and GitHub Actions maintenance workflows — fix a failing test from a CI URL, fix a failing smoke test, add @pytest.mark.slow markers to slow tests, or review a PR against agent-checkable standards. Use when user asks to fix a failing test, fix a smoke test, mark slow tests, or review a PR. Trigger when the user asks you to run the "Write a PR For A Failing Test", "Fix A Failing Smoke Test", "Mark Slow Tests", or "Review PR According to Agent-Checkable Standards" workflow.

UKGovernmentBEIS

testing-security

testing

432

ensure-test-coverage

Ensure test coverage for a single evaluation - both reviewing existing tests and creating missing ones. Analyzes testable components, checks tests against repository conventions, reports coverage gaps, and creates or improves tests. Use when user asks to check/review/create/add/ensure tests for an eval. Use whenever you are asked to review an evaluation that contains tests, or whenever you need to write a suite of tests. Do NOT use for fixing a specific failing CI test (use ci-maintenance-workflow instead).

UKGovernmentBEIS

testing-security

testing

431

feature-spec

Write browser-based Capybara feature specs for WikiEduDashboard controllers and views. Use this skill when asked to improve test coverage, write feature specs, add browser tests, or cover a controller with specs.

WikiEducationFoundation

testing-security

code-quality

430

electrobun-rpc

Use when working with Electrobun's RPC system — defineElectrobunRPC, Electroview.defineRPC, ElectrobunRPCSchema types, bun-to-renderer and renderer-to-bun communication. Activates automatically when RPC code is present.

milady-ai

testing-security

code-quality

430

electrobun-core

Use when working on any Electrobun desktop app — BrowserWindow, BrowserView, events, app lifecycle, ApplicationMenu, Tray, and electrobun.config.ts. Activates automatically when editing Electrobun project files.

milady-ai

testing-security

testing

430

electrobun-kitchen-sink

Use when working with the Electrobun Kitchen Sink testing app — running tests, understanding the feature manifest, navigating the test runner UI, operating playground windows, or adding new test coverage. Also activates for questions about the defineTest() pattern, AUTO_RUN mode, or the manifest generator/validator scripts.

milady-ai

testing-security

testing

430

electrobun-testing

Use when writing Electrobun tests, adding test coverage to the Kitchen Sink, implementing the defineTest() pattern, generating new test suites, understanding what the kitchen sink tests, or reverse-engineering component behaviour from test source. Activates on test authoring, test framework, or test-driven development questions.

milady-ai

testing-security

testing

425

nuxt-test-utils-skilld

ALWAYS use when writing code importing "@nuxt/test-utils". Consult for debugging, best practices, or modifying @nuxt/test-utils, nuxt/test-utils, nuxt test-utils, nuxt test utils, test-utils, test utils.

nuxt-modules

testing-security

testing

423

e2e-testing

Run, debug, and fix Playwright E2E tests locally. Use when writing new E2E tests, debugging failing tests, or iterating on test fixes before pushing to CI.

iota-uz

testing-security

testing

418

evidence-heavy-evaluator

Generate an evidence-first, read-only repository evaluation report with deterministic scoring and actionable recommendations. Use when the user asks to assess readiness, maintainability, release-readiness, documentation gaps, or engineering health and wants auditable artifacts (`json` + `markdown` + raw command logs).

0xSero

testing-security

testing

414

ab-test-setup

Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.

Dokhacgiakhoa

testing-security

testing

414

e2e-testing-patterns

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

Dokhacgiakhoa

testing-security

testing

414

javascript-testing-patterns

Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.

Dokhacgiakhoa

testing-security

testing

414

performance-testing-review-multi-agent-review

Use when working with performance testing review multi agent review

Dokhacgiakhoa

testing-security

testing

414

python-testing-patterns

Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.

Dokhacgiakhoa

testing-security

testing

414

tdd-master-workflow

Comprehensive Test-Driven Development (TDD) cycle.

Dokhacgiakhoa

testing-security

testing

414

tdd-workflow

Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.

Dokhacgiakhoa

testing-security

testing

414

tdd-workflows-tdd-green

Implement the minimal code needed to make failing tests pass in the TDD green phase.

Dokhacgiakhoa

testing-security

testing

414

tdd-workflows-tdd-red

Generate failing tests for the TDD red phase to define expected behavior and edge cases.

Dokhacgiakhoa

testing-security

testing

414

temporal-python-testing

Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.

Dokhacgiakhoa

testing-security

Page 149 / 389