Explore skills
Showing 36241–36270 of 71509 skills
Use when a Chrome extension's messages reach no listener, sendResponse never fires, a port disconnects mid-test, or a web page's access must be proven. Tests runtime.sendMessage, tabs.sendMessage, long-lived ports, externally_connectable and native messaging on a running extension.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexDecides what kind of failure a red CI test is before anyone starts fixing it. Extracts seven failure signals from the runner output, stack trace, run history, and environment metadata, then walks an ordered first-match-wins rule set to exactly one verdict: flaky-known, environment-drift, defect, timeout, flaky-pre-incident, or flake-of-unknown-cause. Emits the verdict together with the alternatives that were rejected and the specific condition each one failed, so the triage decision is auditable rather than asserted. Use when a test has just gone red and the next action depends on whether the cause is a product defect, a non-deterministic test, or drifted infrastructure.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when designing how tests run in CI on any platform (GitHub Actions, GitLab CI, Jenkins, CircleCI): how many shards, which failures are safe to retry, quarantine, artifact retention, per-PR vs nightly cadence, cancel-on-push, timeouts and secrets. CircleCI config patterns are in its references.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when designing or testing a command-line tool's output: a new flag, command or error message, CLI assertions, or flaky tests caused by unstable output. Sets the contract for exit codes, stdout vs stderr, --json output, ordering, color and --help, based on the Command Line Interface Guidelines.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when E2E tests must run on real browsers and devices in BrowserStack Automate, Sauce Labs or LambdaTest: credentials, the WebDriver hub URL and vendor capabilities, a local tunnel for internal apps, session status reporting and a CI matrix sized to the plan's parallel sessions.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when Cloudflare Workers code needs tests locally: Miniflare 3 (workerd-backed), wrangler dev, emulated KV, Durable Objects, R2 and D1 bindings, and in-process tests with Vitest and @cloudflare/vitest-pool-workers.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when a GitHub-hosted repo needs deep semantic static analysis (SAST) beyond pattern matching, such as cross-file taint and data flow: codeql database create and analyze per language, query packs, SARIF upload to code scanning, and suppressions.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when a named framework (GDPR, CCPA, SOC 2, HIPAA, PCI DSS, ISO 27001) and existing evidence need a per-criterion readiness score before an audit, assessor visit or regulator inquiry. Marks each criterion met, partial or not met, records approved exclusions and never claims ready with a gap.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexProcedure for proving that a claimed defect fix actually reached the build under test and actually works. Covers the merge-base ancestry check that proves the running build contains the fix commit rather than trusting a version label, the priority order for choosing which reproduction to re-run, and the VERIFIED / NOT FIXED / BLOCKED verdict table whose governing rule is that any ambiguous, flaky, or unreproducible result resolves to BLOCKED and is never guessed. Scoped to ISTQB confirmation testing (does this specific fix work?), not regression testing (did the fix break something else?), and not triage or severity assignment. Use when a developer has marked a defect Fixed and someone must decide whether it moves to Verified or back to Reopened.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when a deploy should be blocked by any incompatible API contract across protocols. Combines Pact can-i-deploy, oasdiff for OpenAPI, graphql-inspector for GraphQL and buf breaking for Protobuf into one go/no-go CI step with severity thresholds and a reason per finding.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when a pull request needs readable coverage feedback rather than one total. Compares current and baseline coverage (LCOV, Cobertura or JSON) and reports per-file line and branch deltas, new files and hidden drops, with a one-line summary for the PR comment.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when a project needs fuzz testing, a fuzz campaign must be written or maintained, or fuzzer crashes need triage. Picks libFuzzer, AFL++, cargo-fuzz, Go fuzzing, Atheris or Jazzer by language, then covers fuzz targets, seed corpora, dictionaries, sanitizers, crash triage and CI smoke fuzzing.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when a Python project (pytest or unittest) needs code coverage: coverage run, branch coverage, combining parallel xdist data, .coveragerc source, omit and fail_under settings, and terminal, HTML, Cobertura XML, LCOV or JSON reports for CI.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when designing or adding tenant isolation tests to a multi-tenant app, adding a CI leak gate, or investigating a leak. Inventories tenant-bearing surfaces, then tests read-by-ID, list leaks, spoofed tenant IDs, JWT replay, storage IDOR, search, jobs and caches, plus Postgres row-level security.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexConfigures Cucumber for BDD scenarios - Cucumber-JVM (Java/Kotlin via JUnit 5), Cucumber-JS (Node), Cucumber-Ruby. Authors `.feature` files in Gherkin, writes step definitions in the host language, runs via the framework's runner, integrates with JUnit XML reporting. Use when the user mentions Cucumber, Gherkin, `.feature` files, or behavior-driven (BDD) tests in Java, Kotlin, JavaScript, or Ruby, as the canonical wrapper for any of the three official implementations.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when a Playwright suite needs hosted analytics across runs: flakiness over time, slowest tests and pass-rate trends. Sets up Currents.dev with @currents/playwright, currents.config.ts, the reporter, traces, videos and screenshots, and runs via npx pwc.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when a dependency, image or SBOM scan returned more CVEs than the team can fix and someone must decide what to fix first. Ranks each CVE by EPSS exploit probability and CISA KEV status, applies VEX and reachability, and sorts findings into Fix-Now, This-Sprint, Backlog or Accept-Risk.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse whenever a project writes, fixes or upgrades Cypress E2E tests: cypress.config.ts, replacing cy.wait sleeps with assertions, cy.intercept network stubs, fixtures and cy.task, cy.clock, cy.origin logins, cy.session commands, the Cypress 16 upgrade, and Cloud parallel runs.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse 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
Stars: 0Claude CodeCodexUse 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
Stars: 0Claude CodeCodexUse 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
Stars: 0Claude CodeCodexUse 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
Stars: 0Claude CodeCodexUse 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
Stars: 0Claude CodeCodexUse 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
Stars: 0Claude CodeCodexUse 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
Stars: 0Claude CodeCodexUse 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
Stars: 0Claude CodeCodexUse 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
Stars: 0Claude CodeCodexUse 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
Stars: 0Claude CodeCodexUse 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
Stars: 0Claude CodeCodex