Showing 39541–39570 of 77200 skills
Use when scoping a new data product or formalizing checks on an existing one. Reads a data PRD, dataset README or lineage doc and writes a data contract: schema with types, nullability and PII flags, freshness SLA, volume bounds, distribution rules and owner, for dbt, Great Expectations or Soda.
MaarkssDN/Birthub-360
Use when a data pipeline needs one CI step that fails the build when data quality drops. Gathers check results from dbt, Great Expectations or Soda, applies severity-aware thresholds and returns a single go/no-go decision with a reason per check.
MaarkssDN/Birthub-360
Use when load tests or production telemetry show the database is the bottleneck. Reads EXPLAIN or EXPLAIN ANALYZE output from PostgreSQL, MySQL or SQLite, finds the main cost (sequential scans, nested loops, sort spills, missing or unusable indexes) and proposes the index or query rewrite.
MaarkssDN/Birthub-360
Use whenever a dbt project needs data tests or CI gates: generic, singular and custom-macro tests, model assertions, reading failures from run_results.json and gating dbt build on the results.
MaarkssDN/Birthub-360
Use when a service that takes two or more locks hangs in production with no error, or before a release when lock order across code paths was never checked. Records lock order, finds cycles, uses lock timeouts to fail instead of hang, and reads jstack or gdb thread dumps.
MaarkssDN/Birthub-360
Use before training to catch train-test leakage and data integrity problems in tabular, NLP or vision data, and to rerun the same suite on production samples for drift. Runs Deepchecks data integrity, train-test validation and model evaluation suites and gates CI on passed conditions.
MaarkssDN/Birthub-360
Use when LLM or RAG evaluation should run as pytest tests: DeepEval LLMTestCase, built-in metrics such as G-Eval, answer relevancy, faithfulness, contextual recall and precision, hallucination, bias and toxicity, deepeval test run with assert_test, and the Confident AI dashboard.
MaarkssDN/Birthub-360
Use when a defect has been confirmed in production and the team must name which class of gap let it through before deciding what to build. Classifies it as a test, process or tooling gap and one of thirteen sub-patterns at the earliest layer that should have caught it, with the fix, without blame.
MaarkssDN/Birthub-360
Use when a team has no Definition of Done, wants to revise it, or is about to mark a story or PR done without checking it. Drafts a starter DoD and a per-PR checklist, and audits work line by line against an existing DoD with repository evidence, never on self-attestation.
MaarkssDN/Birthub-360
Use when writing or reviewing .github/dependabot.yml for a GitHub repo: required keys, ecosystems, directories and schedules, plus ignore rules, grouped PRs, allow lists, labels, PR limits, target branches, versioning strategy and security-only updates.
MaarkssDN/Birthub-360
Use when a repo needs dependency CVE scanning (SCA) in CI, a team is choosing between native audits (npm audit, pip-audit, cargo audit), OSV-Scanner and Snyk, or findings need triage. Scans lockfiles with thresholds, checks packages were seen, outputs SARIF and allows only expiring ignores.
MaarkssDN/Birthub-360
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
MaarkssDN/Birthub-360
Use whenever a React Native app needs end-to-end tests with Detox: gray-box runs inside the app, by.id, by.text and by.label matchers, waitFor for extra sync, and the Jest runner. Flutter is flutter-testing; cross-platform black-box is appium-testing; YAML flows are maestro-flows.
MaarkssDN/Birthub-360
Use when tests need the app plus several real services (database, cache, queue) started together. Writes a compose.test.yaml with healthcheck-ordered startup, per-job project names for parallel CI, --wait and --exit-code-from gating, and clean teardown with volumes removed.
MaarkssDN/Birthub-360
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
MaarkssDN/Birthub-360
Use whenever the task is to write, add, fix or review .NET unit tests in C#, F# or VB.NET, even a quick test for one method: xUnit.net by default, plus NUnit and MSTest. Covers Fact and Theory tables, fixtures, mocking, FluentAssertions, async tests and coverage with dotnet test.
MaarkssDN/Birthub-360
Use when a disaster-recovery drill for one service is being planned, run or written up, or a new tier-1 service has no drill. Writes a runbook with RTO and RPO per tier, a pre-drill checklist, timed failover and failback, abort rules, an audit-ready report, and backup and restore checks.
MaarkssDN/Birthub-360
Use when CI is slow or dominated by end-to-end tests, flaky failures are rising, or for a quarterly suite review. Ranks every E2E test by ROI (regressions caught vs runtime, flake rate and maintenance) and recommends which to retire, move to a lower layer or fix.
MaarkssDN/Birthub-360
Use before changing analyzers, synonyms, boosts or query templates on Elasticsearch, OpenSearch or Solr search, so a relevance baseline exists. Builds judgment lists and _rank_eval tests with precision, recall, MRR and DCG, plus OpenSearch and Solr specifics in its references.
MaarkssDN/Birthub-360
Use whenever an Electron desktop app needs end-to-end tests, or a Spectron suite must be migrated: Playwright's _electron.launch, renderer windows as Pages, main-process checks via electronApp.evaluate, and IPC and DOM assertions from one suite.
MaarkssDN/Birthub-360
Use when deciding what code coverage level embedded C/C++ needs (statement, branch, MC/DC) and wiring gcov or llvm-cov into the build: host vs QEMU instrumentation, MISRA-C and DO-178C expectations by safety level, and report formats.
MaarkssDN/Birthub-360
Use para validar uma jornada completa do produto (lead→enriquecimento→conversão→Bitrix; empresa→enriquecimento→CRM; IA→dados→resposta→persistência), não um componente isolado. Um módulo não é funcional só porque suas partes passam em isolamento — valida happy path, erro, reload, duplicidade, autorização, integridade e observabilidade ao longo de toda a cadeia.
MaarkssDN/Birthub-360
Use when an SLO and error budget exist but nothing proves burn-rate alerts fire or the release freeze engages when the budget runs out, or MTTR and MTBF numbers can't be reproduced. Tests error-budget math, burn-rate alerts, exhaustion and freeze triggers, and incident metric calculations.
MaarkssDN/Birthub-360
Use whenever an Android app needs UI tests in Google's Espresso: onView with perform and check, automatic synchronization instead of sleeps, IdlingResource for app async work, ./gradlew connectedAndroidTest and JUnit XML results.
MaarkssDN/Birthub-360
Use when an event-sourced aggregate gains or changes an event type, snapshots are added, or a CQRS read model is projected from events. Tests given-events/when-command/then-events, replay determinism, upcasting, snapshot equivalence, projections and eventual-consistency windows.
MaarkssDN/Birthub-360
Use when a tabular ML model needs a drift or quality gate in CI, a scheduled monitoring job, or triage of a fired drift alert. Uses Evidently reports with tests for data drift, target drift and performance regression, and a playbook to pick rollback, retrain, quarantine or alert re-tuning.
MaarkssDN/Birthub-360
Use before a QBR, board update or exec review when quality data exists (digests, KPIs, DORA metrics, escaped defects, OKR grades) but the story does not. Writes the executive narrative with the answer first and grouped support beneath it, using the Minto Pyramid and SCQA.
MaarkssDN/Birthub-360
Use when code instrumented with Statsig, Optimizely, Split.io (Harness FME), Amplitude Experiment or VWO needs tests. Initializes the SDK offline from a committed config fixture, pins each test to an arm and checks assignment integrity, with per-vendor references.
MaarkssDN/Birthub-360
Use when a feature has too many unknowns to script (new feature, risky refactor, bug cluster) and the team needs an exploratory test plan. Writes a session-based testing charter: one-sentence mission, 3-7 areas, a 60, 90 or 120 minute time-box, suggested tours and the debrief deliverables.
MaarkssDN/Birthub-360
Use when one test must reproduce a failure that spans HTTP and network layers, such as an incident nobody can recreate with HTTP stubs or TCP chaos alone. Combines WireMock fault stubs (500s, bad JSON, slow replies) with Toxiproxy (latency, loss, resets) and checks the app's resilience.
MaarkssDN/Birthub-360