Showing 39901–39930 of 77205 skills
Use when asked about test distribution or balance: too many E2E tests, slow CI caused by tests, or rebalancing a suite. Counts unit, integration and E2E tests with runtimes, detects ice-cream-cone and hourglass shapes, and recommends target ratios for the codebase's shape.
MaarkssDN/Birthub-360
Use when a suite has outgrown its value and someone is about to delete tests. Sorts candidates into duplicate, tautology, trivial, dead-signal and orphan, and deletes only when all four gate conditions hold, with a written reason, coverage evidence and a named reviewer.
MaarkssDN/Birthub-360
Use whenever someone asks to write a test-run summary, release test status or Slack post from test results, even from a few numbers: pass, fail and skip counts, JUnit XML, Allure JSON, a TestRail, Xray or Zephyr export. Writes the markdown narrative: a pass/fail lead, deltas and failure owners.
MaarkssDN/Birthub-360
Use when a project, release or feature needs a test strategy or master test plan that stakeholders sign off: scope, test types per layer, risk-based prioritization, tools, environments, exit criteria and ownership, plus a budgeted per-risk test plan with owners and effort.
MaarkssDN/Birthub-360
Use when a test suite has grown for a year or more without review and someone needs to know if it is healthy before deleting or rewriting tests. Classifies files by tier, checks the pyramid ratio and flake rate per layer, measures ROI per tier and gives one verdict.
MaarkssDN/Birthub-360
Brings up real backing services (databases, message brokers, browsers, anything dockerizable) as throwaway containers from inside a test process - Java, Node.js, Python, Go, .NET, Ruby and ten other languages - using the Testcontainers library family. Wires the per-test container lifecycle, exposed-port → host-port mapping, wait strategies (port / log / HTTP / SQL), Ryuk-based cleanup, container-to-container networks, and the (experimental) `withReuse` shortcut for local dev. Use when integration tests need a real Postgres / Redis / Kafka / Selenium / etc. and the team wants per-test isolation without hand-rolled docker-compose teardown.
MaarkssDN/Birthub-360
Use when a codebase needs time zone, DST and leap-year test coverage derived from its own date and time code. Finds where times are stored, computed, displayed, scheduled or billed, picks the edge cases that matter and writes test stubs using the language's fake-clock library.
MaarkssDN/Birthub-360
Use when tests or dev environments need TCP-level network faults without Kubernetes or paid tools. Runs Toxiproxy between client and upstream and applies latency, bandwidth, slow close, timeout, slicer, data limit and reset toxics through its control API.
MaarkssDN/Birthub-360
Use before instrumenting a new feature, when spans have grown with no agreed shape, or after an incident where debugging stalled on missing attributes. Writes a trace spec per feature (root and child spans, key attributes per OpenTelemetry conventions) that drives code review and trace tests.
MaarkssDN/Birthub-360
Use for test coverage audits, finding requirements without tests, sprint-end coverage reviews or compliance documentation. Builds a requirements-to-tests traceability matrix from a test case repository and Jira, Linear or GitHub Issues, with orphaned cases and requirements and a coverage summary.
MaarkssDN/Birthub-360
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
MaarkssDN/Birthub-360
Use when adopting one IaC misconfiguration scanner for Terraform, CloudFormation, Kubernetes, Helm, Dockerfiles and ARM, or migrating off tfsec: trivy config with severity gating, .trivyignore suppressions, custom Rego checks and SARIF for GitHub code scanning. Legacy tfsec is in its references.
MaarkssDN/Birthub-360
Use when container images need one scanner for vulnerabilities, secrets, misconfigurations and licenses: trivy image with severity filters, SARIF or JSON output, .trivyignore suppressions, --ignore-unfixed and scanner toggles. For a standalone SBOM use syft-generation.
MaarkssDN/Birthub-360
Use when a terminal UI (TUI) app needs tests that catch layout regressions. Captures rendered terminal frames as SVG or text snapshots and diffs them on each run: pytest-textual-snapshot for Textual, insta for Ratatui, teatest for Bubble Tea, ink-testing-library for Ink.
MaarkssDN/Birthub-360
Use whenever C# code in a Unity game-engine project needs tests that use the Unity runtime or editor: Unity Test Framework EditMode vs PlayMode tests, [Test] and [UnityTest], assembly definitions, the Test Runner window, batch-mode command-line runs and CI. Not the ThrowTheSwitch C library.
MaarkssDN/Birthub-360
Use whenever pure C code for 8-bit MCUs, Cortex-M or embedded Linux needs unit tests with ThrowTheSwitch Unity (not the Unity game engine): TEST_ASSERT families, setUp and tearDown, RUN_TEST, the test runner generator, config defines and CI via Ceedling JUnit XML.
MaarkssDN/Birthub-360
Use whenever C++ Unreal Engine code needs tests that use the engine, editor or UMG UI: the Automation Test Framework's simple and complex tests, Automation Spec (Describe, It, latent tests), latent commands, the Automation Driver for UI input, Session Frontend and command-line runs in CI.
MaarkssDN/Birthub-360
Use when a Varnish caching layer or VCL change needs tests: varnishtest VTC files with server, client and varnish blocks, grace and saint modes, PURGE handlers with ACLs, and surrogate-key invalidation with the xkey vmod.
MaarkssDN/Birthub-360
Use when HNSW or IVF parameters are being tuned, an embedding model is swapped, or vector search recall was never measured. Builds brute-force ground truth, measures recall@k against latency and detects embedding drift for Qdrant, Weaviate, pgvector, Pinecone, Elasticsearch k-NN and Milvus.
MaarkssDN/Birthub-360
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".
MaarkssDN/Birthub-360
Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core Web Vitals, Bot Management, Fluid compute, or cost breakdown requests.
MaarkssDN/Birthub-360
Use when a scanner flags a CVE that analysis shows is not exploitable in your product, and a machine-readable assertion is needed instead of deleting the finding. Writes and validates OpenVEX statements (not_affected, affected, fixed, under_investigation) with vexctl and attaches them to images.
MaarkssDN/Birthub-360
Use when visual diffs are already classified and CI needs one binding go/no-go: blocks on regressions or on intended baseline changes without sign-off from a reviewer who is not the author, fails closed when the classifier did not run, and writes visual-gate.json and .md.
MaarkssDN/Birthub-360
Use when designing a color palette, reviewing a component's colors or auditing CSS for contrast: WCAG 2.2 text, large-text and non-text contrast ratios (4.5:1, 3:1) at AA and AAA, the measurement formula and bulk checks over design tokens.
MaarkssDN/Birthub-360
Use after an accessibility scan across many pages (pa11y-ci, axe over a sitemap, Lighthouse batch) when the team needs a shareable conformance report. Groups violations by WCAG 2.2 success criterion and level, flags pages that were not scanned and writes a summary plus per-page detail.
MaarkssDN/Birthub-360
Use when building or reviewing keyboard-only support or a modal, drawer or popover's focus handling: WCAG 2.2 keyboard access, no keyboard traps, shortcuts, focus order, visible and unobscured focus, with test scripts and the focus-trap pattern (focus on open, Escape, restore).
MaarkssDN/Birthub-360
Use when a web app has no E2E tests yet, a team is choosing or replacing an E2E framework, or a first browser test must go green. Explains what E2E covers, picks between Playwright, Cypress, Selenium, WebdriverIO, Puppeteer, TestCafe and cloud grids, and the traps that make suites flaky.
MaarkssDN/Birthub-360
Use when a PWA ships browser web push and the subscription lifecycle needs release tests: pushManager.subscribe with VAPID keys, pushsubscriptionchange, push event delivery, push-service responses (201, 410, 413, 429) and unsubscribe. Native APNs and FCM are push-notification-test-author.
MaarkssDN/Birthub-360
Use when a page feels slow to respond while LCP and CLS are green, or key interactions (form submit, modal open, route change) need an INP budget in CI. Breaks Interaction to Next Paint into input delay, processing and presentation, asserts per-interaction budgets in Playwright and finds long tasks.
MaarkssDN/Birthub-360
Use when a team needs WebdriverIO E2E tests: npm init wdio scaffolding, services for Sauce Labs, BrowserStack, Appium and DevTools, spec, Allure and JUnit reporters, and Mocha, Jasmine or Cucumber, combining the WebDriver protocol with a plugin ecosystem.
MaarkssDN/Birthub-360