Showing 39721–39750 of 77200 skills
Use whenever RabbitMQ producers or consumers (pika, amqplib, RabbitMQ.Client, spring-amqp) need tests: work queues, pub/sub, routing, topics and RPC, publisher confirms, ack, nack and requeue, durable and quorum queues, with the Testcontainers RabbitMQ image.
MaarkssDN/Birthub-360
Use when a bug only appears under load on shared in-process state (cache, counter, pool, lazy singleton), or a race needs a regression test before the fix. Forces interleavings with barriers and latches, and runs ThreadSanitizer, go test -race with goleak, or jcstress for the JVM.
MaarkssDN/Birthub-360
Use when a RAG pipeline (retriever plus generator) or an agent needs the widest set of evaluation metrics: Ragas faithfulness, response relevancy, context precision and recall, noise sensitivity, factual correctness, tool-call accuracy, agent goal accuracy and rubric scoring.
MaarkssDN/Birthub-360
Use whenever npm audit, OSV-Scanner or Snyk reports too many vulnerabilities and only the ones that matter should count. Finds dependencies the code never uses with knip or depcheck (JS), vulture (Python) or cargo-machete (Rust) and downranks their CVEs. EPSS and KEV: cve-exploitability-triage.
MaarkssDN/Birthub-360
Use before fixing a bug or adding a feature in any language, even a one-line fix: reproduce it with a failing test first, watch it fail for the right reason, make the smallest change that passes, refactor, and show the test output before saying it is fixed or works.
MaarkssDN/Birthub-360
Use when Redis is the app's cache and its behavior needs tests, or when choosing a cache invalidation strategy: TTLs, cache-aside write and invalidate, eviction under memory pressure, pub/sub invalidation across nodes and tenant key namespaces, plus stampede and stale-while-revalidate patterns.
MaarkssDN/Birthub-360
Use when the regression suite is so large that PR-time CI is the bottleneck. Builds a CI step that runs only tests affected by the PR's changed files (from coverage maps or Bazel rdeps), plus previously failing and new tests, while a periodic full run guards against a stale map.
MaarkssDN/Birthub-360
Use when a service is about to ship and its release steps live only in people's heads or a chat thread, or a shared release window needs its cutover order. Writes a six-phase runbook (pre-flight, smoke, canary, promote gate, rollout, verification) with baseline-relative criteria and rollback paths.
MaarkssDN/Birthub-360
Use when writing or reviewing renovate.json for Mend Renovate on GitHub, GitLab, Bitbucket, Azure DevOps or Gitea: preset extends, schedules, PR limits, vulnerability alerts, packageRules matching with automerge, ignored dependencies and labels.
MaarkssDN/Birthub-360
Use when a .NET project starts BDD, migrates from SpecFlow (end-of-life 2024-12-31) or maintains a legacy SpecFlow suite. Configures Reqnroll: Gherkin .feature files, [Given/When/Then] C# bindings, hooks and dotnet test runs.
MaarkssDN/Birthub-360
Use whenever Java/JVM API tests need writing or fixing: loose assertions that let an empty 200 pass, slow sequential suites, or hand-rolled HTTP clients. Writes REST Assured given/when/then tests: status, JSON and XML path checks, auth, reusable specs, schema checks, Maven or Gradle and CI reports.
MaarkssDN/Birthub-360
Use when a stateful REST API (resources created, read, changed and deleted in sequence) needs fuzzing that finds multi-step bugs stateless fuzzers miss. Runs Microsoft RESTler from an OpenAPI spec (compile, test, fuzz-lean, fuzz) and reports 5xx errors, resource leaks and hierarchy violations.
MaarkssDN/Birthub-360
Use for any risk-based testing artifact: a risk matrix or register with likelihood x impact scores, a risk-storming session, calibrating ratings against real defects, or mapping each risk to the tests and monitors that cover it. Supports light and heavy methods (FMEA, Cost of Exposure).
MaarkssDN/Birthub-360
Use when an app supports right-to-left languages (Arabic, Hebrew, Persian, Urdu). Runs the suite under RTL locales, checks dir=rtl, mirrored layout, icons and alignment, logical CSS properties instead of left and right, and captures screenshots per locale for review.
MaarkssDN/Birthub-360
Use whenever the task is to write, add, fix or review Rust tests, even one quick #[test]: assert macros, should_panic, Result-returning tests, integration and doc tests, rstest parametrization, mockall, coverage with cargo-llvm-cov and Criterion benchmarks.
MaarkssDN/Birthub-360
Use when a business transaction spans two or more services and a mid-sequence failure must be undone, or compensation logic just changed. Tests orchestrated and choreographed sagas: each compensating step, partial failures, idempotent compensations and the outbox for atomic publish.
MaarkssDN/Birthub-360
Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.
MaarkssDN/Birthub-360
Use whenever an API has an OpenAPI or GraphQL schema and needs tests generated from it: fuzzing every endpoint for 5xx errors and schema violations. Runs Schemathesis from the CLI or pytest, picks the conformance checks and gates CI on failures as the API evolves.
MaarkssDN/Birthub-360
Use when a feature needs manual screen-reader testing before sign-off: step-by-step scripts for NVDA, JAWS, VoiceOver or TalkBack with keystrokes and expected announcements, WCAG 2.2 checklists per page type, widget keystroke matrices and a guided session with a signed report.
MaarkssDN/Birthub-360
Use when a secret is found in code or history, or for scheduled rotation: identify the provider, rotate the credential through its API (AWS IAM, GitHub, Stripe, GCP, Azure, Twilio, Slack and more), revoke the old one, log the audit trail and link the post-mortem. Scrubbing git history is not enough.
MaarkssDN/Birthub-360
Use when E2E tests need a reproducible seed dataset and the project has none, or the existing seed has drifted. Picks a representative cross-section of users, orgs and data, generates rows with the project's factory library, checks in the fixture and wires it into test setup.
MaarkssDN/Birthub-360
Use when cross-browser tests must run on a self-hosted Selenium Grid 4 for data residency or cost: standalone or hub-and-node, the Docker images, node registration, session queue tuning and observability. Managed grids are cloud-grid-e2e; choosing browsers is browser-matrix-strategy-reference.
MaarkssDN/Birthub-360
Use when a project is already on Selenium WebDriver and needs tests written, fixed or upgraded in Java, Python, C# or other bindings: Selenium Manager drivers, locators, explicit waits, page objects, BiDi console errors, Grid in Docker, JUnit XML. New projects usually pick Playwright.
MaarkssDN/Birthub-360
Use when a team runs Semgrep or wants a low-friction static analysis (SAST) gate without building a code database: Registry rulesets and custom YAML rules, semgrep ci with diff-aware baselines, nosemgrep suppressions, path filters, severity filters and JSON, SARIF, GitLab or JUnit output.
MaarkssDN/Birthub-360
Use when a feature pushes updates over Server-Sent Events (text/event-stream) and needs tests: EventSource events and errors, the stream format, reconnect with Last-Event-ID replay, retry intervals and per-origin connection limits, plus k6 load tests. Two-way messaging is websocket-tests.
MaarkssDN/Birthub-360
Use when a serverless project (SAM, serverless.yml, Wrangler, Vercel or Netlify functions) has no integration tests yet. Inventories functions and event sources, picks a local emulator per function, generates test events, asserts cold-start and timeout budgets, and emits the tests and CI config.
MaarkssDN/Birthub-360
Use when a service worker needs lifecycle tests, users are stuck on an old version after deploy, or caching and offline behavior is untested. Tests each state change from installing to activated, waitUntil, skipWaiting and clients.claim, update() and a clean v1 to v2 upgrade with Playwright.
MaarkssDN/Birthub-360
Use whenever a web app's session layer needs tests, in any framework: cookie flags (Secure, HttpOnly, SameSite), session ID regeneration on login, idle and absolute timeouts, concurrent-session limits, logout on all devices, CSRF tokens and session binding, per OWASP ASVS V3.
MaarkssDN/Birthub-360
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
MaarkssDN/Birthub-360
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
MaarkssDN/Birthub-360