Explore skills
Showing 39481–39510 of 77079 skills
Generates boundary-value test cases from typed input specifications - for each input field, produces the canonical 6-point set (one below, at, and above the lower bound; one below, at, and above the upper bound) plus equivalence-class representatives. Emits cases as parameterized test inputs (pytest @parametrize / Jest test.each / xUnit InlineData / etc.). Use when a function or endpoint has numeric / string-length / collection-size constraints and the team needs systematic edge-case coverage.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when .proto files need a CI gate or a buf failure needs debugging: buf build, buf lint (STANDARD rules), buf breaking against a git or BSR baseline, buf format, and choosing the rule category per consumer. Explains which changes break wire or generated code and why.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when a team wants a coordinated bug bash before a release or after a big change instead of an ad-hoc 'everyone test for an hour'. Prepares the charter, data, environments and sign-up, runs roles, a shared board and live triage, scores findings and writes the same-day wrap-up.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when someone reports a problem informally, a CI failure (JUnit XML, Allure, pytest or Playwright output) must become a bug report, or a draft needs a quality check before filing. Fills summary, environment, steps, expected vs actual and severity rationale, then checks each field is usable.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when defect counts or reports are wrong (missing top-severity bugs, fixed items counted as new, unmerged duplicates) or bug filing and transitions need automating. One workflow for Jira, Linear, GitHub Issues and Azure DevOps: dedupe before filing, severity vs priority, lifecycle and CI filing.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse whenever a Node.js or TypeScript service uses BullMQ and its queues or workers need tests: producers, worker processors, retries, backoff and repeat jobs, FlowProducer parent-child jobs and QueueEvents, against real Redis (Docker, Testcontainers) or ioredis-mock.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexGovernança de filas, workers BullMQ e Redis no Birth Hub 360 (worker.ts). Regras para retry com exponential backoff, Dead-Letter Queues (DLQ), deduplicação de jobs vs idempotência de negócio e prevenção de memory leak.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse whenever a user saw another user's or tenant's data, or a per-user response goes through a shared cache, Redis or a CDN, or a cache key is designed or changed. Checks the key holds every value the response depends on (tenant, user, scope, locale), writes the fixed key, Vary header and tests.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when CDN or browser caching needs tests: purges and invalidations on Cloudflare, Fastly (surrogate keys) and CloudFront, end-to-end write, purge and fresh-read checks, propagation delay and cache-status headers, plus browser Cache-Control, ETag and service-worker caching with Playwright.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when a C project wants Unity, CMock and CException run by one build command, or CMock mocks need writing or reading: Ceedling project scaffolding, project.yml, test tasks, JUnit XML, gcov coverage, host vs cross builds and CI. The Unity assertion API is unity-test-framework-c.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse whenever Python Celery tasks need unit or integration tests: pytest-celery celery_app and worker fixtures, apply() for synchronous calls, why task_always_eager misleads, and mocking task.retry to test retry behavior, for function and class-based tasks.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when a chaos experiment is already designed and a fault is about to be injected into a running system. Sets the go/no-go gates (non-production, healthy baseline, live monitoring, tested rollback), blast-radius bound, abort criteria, inject and abort commands and the recovery check.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when scoping a chaos engineering experiment before running it: a steady-state hypothesis, real-world faults (latency, node or region failure), blast radius, automation and the verdict, with a five-check validation of the hypothesis and LitmusChaos and Gremlin setup. Chaos Mesh has its own skill.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when a system runs on Kubernetes and fault experiments should be declared as CRDs next to the workloads. Configures Chaos Mesh pod, network, stress, IO, time, DNS, kernel and HTTP faults, label selectors, namespace limits on blast radius, schedules and the dashboard.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when a dashboard renders charts that need regression tests, before a chart library upgrade or after a theme change. Canvas charts (Chart.js) get screenshot and toDataURL diffs, SVG (D3) gets normalized structure snapshots, and Vega or Vega-Lite specs get schema and compile checks.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when infrastructure code (Terraform, CloudFormation, Kubernetes, Helm, ARM, Serverless, CDK) needs security scanning with the broadest built-in rule set: Checkov with custom Python checks, SARIF and JUnit output, and a baseline so CI fails only on new findings. Single-tool option: trivy-config.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse when visual regression tests run on Chromatic Cloud for Storybook, Playwright or Cypress: the chromatic CLI, baselines, TurboSnap, UI Review, CI gating and reading exit codes to tell visual changes from errors.
MaarkssDN/Birthub-360
Stars: 0Claude CodeCodexUse 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 CodeCodex