Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 66781–66810 of 70187 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| synthetic-data-toolkitMaarkssDN/Birthub-360Use whenever someone asks for test factories or a FactoryBot setup, even a quick one: factories with traits and associations (Ruby, Rails), Mimesis bulk data (Python), Bogus Faker<T> builders (.NET), or which generator fits. Same fixture in each tool; plain fake values stay with faker-data. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| synthetic-monitor-authorMaarkssDN/Birthub-360Use when a critical user journey needs continuous checks in production, or monitor coverage was never derived from real usage. Writes a synthetic monitor for Datadog, Pingdom, Checkly or New Relic with browser or API steps, cadence, checks and alerts, and ranks unmonitored journeys from RUM data. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| synthetic-pii-generatorMaarkssDN/Birthub-360Use when seeding non-production environments, building demo data, or replacing real personal data in copied datasets. Generates fake but valid-looking PII: names, emails, phones, addresses, national IDs and SSNs, Luhn-valid test card numbers and birth dates, never real people's data. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| tailwind-token-auditorMaarkssDN/Birthub-360Governança do Tailwind CSS v4 (@tailwindcss/vite e @theme em src/styles/globals.css) no Birth Hub 360. Audita classes arbitrárias, proíbe aliases legados em componentes novos e exige os tokens semânticos canônicos do projeto. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| tcm-case-managementMaarkssDN/Birthub-360Use when managing test cases in TestRail, Xray, Zephyr Scale, Allure TestOps or Qase: writing cases from a spec, organizing suites, steps with expected results, linking requirements, bulk importing from CSV or JSON, migrating between tools or mass edits. Pushing run results is test-management-sync. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| tddMaarkssDN/Birthub-360Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| teachMaarkssDN/Birthub-360Teach the user a new skill or concept, within this workspace. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| tenant-onboarding-test-authorMaarkssDN/Birthub-360Use when a tenant onboarding or offboarding flow is added or changed, or before a compliance review: tests for account creation, isolation from the first API call, default quotas, billing links, seed data, idempotent re-provisioning and full deletion on teardown. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| test-case-anatomy-referenceMaarkssDN/Birthub-360Use when writing a test case template, reviewing a batch of test cases for quality, or migrating cases between tools. Lists the ISO/IEC/IEEE 29119-3 and ISTQB test case fields, maps them to TestRail, Xray, Zephyr Scale, Allure TestOps and Qase, and gives a PASS, WEAK or FAIL review rubric. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| test-case-from-live-featureMaarkssDN/Birthub-360Use when a feature has no story, acceptance criteria or docs, only a running app, recording, screenshot or verbal brief, and it needs test cases. Explores the feature and applies HTSM/SFDPOT, Whittaker attacks, FEW HICCUPPS oracles and ISO 25010 to produce a test case matrix. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| test-case-ideation-from-storyMaarkssDN/Birthub-360Use when a thin or ambiguous user story or spec needs its test cases listed and agreed before automation. Produces a markdown test case matrix (id, title, precondition, steps, expected, tier) covering happy, alternate, boundary and negative paths, ready for TestRail, Qase or Xray. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| test-code-conventionsMaarkssDN/Birthub-360Pure-reference catalog of test-code conventions: AAA structure (Arrange / Act / Assert), per-test single-responsibility, descriptive naming (`{sut}_{scenario}_{expected}`), assertion specificity, mocking rationale (state vs behavior, fake vs mock), fixture-coupling rules, the magic-number / hard-coded-string anti-patterns, and step design (§11: FIRST principles, step granularity, the mechanical → page → business abstraction layers, the rule-of-three extraction heuristic, declarative phrasing); the E2E selector-priority, web-first-assertion, and step-grouping conventions live in references/. Use as the shared rule book a test-code review cites back to, or as onboarding for what makes a test code-reviewable; to score a test's quality on weighted axes use test-design-scorecard, and for setup/teardown isolation specifically use test-isolation-patterns. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| test-coverage-targeterMaarkssDN/Birthub-360Use when a team can write only a handful of new tests and must pick which uncovered code matters most, or when some modules lose coverage while the total looks fine. Ranks uncovered branches in the diff by complexity, churn and test cost, and tracks per-file coverage drift. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| test-data-patternsMaarkssDN/Birthub-360Use when choosing how a test suite builds its test data, or when fixtures have drifted into shared mutable state. Explains Test Data Builder, Factory, Object Mother, fixture composition, snapshots and production-data anonymization, and when each fits, before picking a tool. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| test-design-scorecardMaarkssDN/Birthub-360Use when a test diff needs a graded coaching review rather than a merge verdict: onboarding a new engineer, ramping up test discipline, or a quarterly per-author trend. Scores tests 1-5 on six design axes with explicit anchors and writes growth-framed feedback. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| test-effort-estimationMaarkssDN/Birthub-360Use when an epic or release is split into testable areas and someone must commit test capacity. Produces a PERT three-point estimate as ranges, with a named assumptions ledger and a split across developer, automation and exploratory work; also classifies a change set's shape from git history. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| test-framework-architecture-auditMaarkssDN/Birthub-360Use when a test automation framework has grown without structural review, before a big refactor, or when its written conventions may no longer match the code. Grades eight axes PASS, WARN or FAIL: page objects, base classes, fixtures, helpers, naming, waits and retries, convention drift and CI. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| test-framework-blueprintMaarkssDN/Birthub-360Use when designing a test automation framework from scratch or re-architecting one that grew organically. Walks seven steps from inventorying the app to runner, layout, fixtures, object model, data and mocks, reporting, CI and conventions, and outputs a written blueprint with a build order. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| test-isolation-patternsMaarkssDN/Birthub-360Pure reference catalog of test-isolation and fixture-lifecycle patterns - the four-phase test pattern (Meszaros), fixture scope (per-test / per-describe / shared / global), the Fresh-Fixture vs Shared-Fixture trade-off (Fowler), parallel-safety patterns, and cleanup discipline (afterEach / afterAll / tagged-cleanup), plus a pattern-selection guide and a worked leaking-state diagnosis. The database-isolation strategies (transaction-rollback / database-per-worker / template-database) and network / external-service stubbing live in references/. This is the architecture-tier reference, not a file-level fixture-coupling style rule. Use when designing fixture scope and isolation strategy, auditing fixture coupling or retry/wait policy, or moving a suite to parallel execution. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| test-management-syncMaarkssDN/Birthub-360Use when CI test results must flow into TestRail, Xray for Jira or Zephyr Scale without manual copying. Maps tests to case IDs, opens a run per build, pushes results in batches and closes runs on main only; vendor details are in its references. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| test-pyramid-balancerMaarkssDN/Birthub-360Use 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. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| test-removal-criteriaMaarkssDN/Birthub-360Use 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. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| test-run-summary-authorMaarkssDN/Birthub-360Use 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. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| test-strategy-authorMaarkssDN/Birthub-360Use 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. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| test-suite-health-auditMaarkssDN/Birthub-360Use 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. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| testcontainersMaarkssDN/Birthub-360Brings 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. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| timezone-test-matrix-builderMaarkssDN/Birthub-360Use 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. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| to-questionnaireMaarkssDN/Birthub-360Turn a decision you can't fully answer into a questionnaire for someone else to fill in. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| to-specMaarkssDN/Birthub-360Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| to-ticketsMaarkssDN/Birthub-360Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker). | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |