agentsclimarketplace

Test

10,621 rows, by stacks then stars

1,559 of these skill files have been read, by 1,201 distinct authors, and what they tell an agent counted. What Test authors agree on, and what they forbid

  • Api test suite builder

    dills122/ai-central/templates/skills/imported/claude-skills/engineering/skills/api-test-suite-builder Skill

    0★ repo

    Use when the user asks to generate API tests, create integration test suites, test REST endpoints, or build contract tests.

    The same file is in 5 other repositories

  • Ab test analysis

    dills122/ai-central/templates/skills/imported/pm-skills/pm-data-analytics/skills/ab-test-analysis Skill

    0★ repo

    Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.

    The same file is in 1 other repository

  • Test architect

    ak-ship/fullstack-agent-skills/skills/test-architect Skill

    0★ repo

    Write unit and integration tests that actually catch bugs — real assertions, real edge cases, real failure modes. Detects the project's framework (Jest, Vitest, Mocha, pytest, Go test) and matches existing conventions. Use when the user says "write tests for", "cover this with tests", "add unit tests", "I need tests for this function", or hands over an untested module. Refuses to write placeholder `expect(true).toBe(true)` tests.

  • Debugging lab notebook

    alinafe82/cognitive-deadlift/skills/debugging-lab-notebook Skill

    0★ repo

    Debug hard failures with reproduction, hypotheses, instrumentation, experiments, and regression proof. Use when bugs are flaky, poorly understood, production-facing, performance-related, or AI starts guessing fixes. NOT for simple bugs that already have a deterministic failing test.

  • Evidence to test

    alinafe82/cognitive-deadlift/skills/evidence-to-test Skill

    0★ repo

    Convert qualitative repo gaps or repeated failures into deterministic tests, fixtures, validators, or checks. Use when a gap, false confidence pattern, validator miss, or repeated review failure should become executable evidence. NOT for writing implementation code before the observable failure is defined or for broad test-suite expansion without a specific gap.

  • Failing test first

    alinafe82/cognitive-deadlift/skills/failing-test-first Skill

    0★ repo

    Require a failing signal before bug fixes or behavior changes. Use when fixing a bug, adding behavior, changing edge cases, or reviewing AI code that lacks proof. NOT for docs-only edits, generated snapshots, or emergency hotfixes with a tracked follow-up test.

  • Bad skill

    alinafe82/cognitive-deadlift/tests/fixtures/bad-repo/skills/bad-skill Skill

    0★ repo

    A vague fixture. Use when testing failure. NOT for production.

  • Good skill

    alinafe82/cognitive-deadlift/tests/fixtures/good-repo/skills/good-skill Skill

    0★ repo

    Validate a well-formed fixture skill. Use when testing the validator happy path. NOT for production assistant behavior.

  • Codebase testing guide

    husnain067/codebase-knowledge-skills/codebase-testing-guide Skill

    0★ repo

    Document the testing setup of a codebase — what framework is used, where tests live, how to run them, what's mocked and how, what fixtures/factories exist, and what testing patterns repeat. Use this skill when the user asks "how do tests work here", "document the test setup", "what's the testing approach", "where are the tests", "how do I write a test in this project", "explain the mocking", or any variant focused on the test suite rather than full architecture. The output is a single Markdown file capturing test framework + config, test file location and naming, mocking and fixture patterns, test helpers, how to run the suite, coverage setup, and notable testing idioms — each documented with real examples copied from the actual codebase. This skill is narrow by design and produces ONLY the testing reference. It does not cover architecture, naming conventions, error handling, or domain vocabulary — point the user to the relevant sister skill if they need those.

  • Two tenant verify

    amineorion/claude-code-safety-skills/skills/two-tenant-verify Skill

    0★ repo

    Verify tenant isolation by exercising a data change as a second tenant and confirming the first tenant's data is invisible — in the running app, not just tests. Use after changing data-access code on a multi-tenant SaaS, before merging, or when the user asks to prove isolation holds or test for leaks end to end.

  • Discipline test is truth

    yli769227-jpg/awesome-claude-code-cn/skills/discipline-test-is-truth Skill

    0★ repo

    测试即结论 —— 完成的定义不是"代码写完",而是"测试结果可验证"。触发: 即将向用户声明任务完成、即将说"应该没问题"、即将合并 PR、即将关闭 issue、即将派 agent 子任务前。任何完成声明必须附带 ✅/❌/⚠️ 三段式测试结论。

  • Three tier test

    nuwansamaranayake/AiGNITEClaudeAssets/three-tier-test Skill

    0★ repo

    Enforces the AiGNITE Chrome to mirror to phone testing sequence with hard checkpoints. Tier one runs Playwright over the Expo web build. Tier two runs a recorded walkthrough on iPhone Mirroring or Android emulator. Tier three runs a manual checklist on a physical device. Each tier must pass before the next starts. Use this skill whenever the user mentions testing a mobile app, verifying a build, QA, asking if a build is ready to ship, or running a three-tier test, even if they do not name the skill by name.

  • Michi scenario test builder

    csepulv/michi/toolkit/skills/michi-scenario-test-builder Skill

    0★ repo

    my approach to building software, embodied in an agent-centric toolkit

  • Pg pressure test

    talgacapri/pm-os/.claude/skills/pg-pressure-test Skill

    no license0★ repo

    Pressure-test any startup idea, product bet, or new feature with the brutal honesty of a Paul Graham YC application review. Six named passes — Pressure Test the Idea (fatal flaws), Validate the Real Problem (vitamin vs painkiller), Map the Real Competition (current behavior + indirect), Find the First 10 Customers (manual traction plan), Build the MVP in 2 Weeks (riskiest assumption only), and the Brutal Verdict (strong / weak / pivot). Use when the user says "pressure test this idea", "is this a real startup", "would PG fund this", "kill or keep this idea", "is this a vitamin or a painkiller", "what's the riskiest assumption", "find me my first ten customers", "scope an MVP", "brutal feedback on this concept", or pastes a startup idea, feature concept, or one-line pitch. Triggers on `/pg-pressure-test`, `/pressure-test`, `/paul-graham`, `/brutal-verdict`, or any explicit request for PG-style critique.

  • Test backend

    talgacapri/pm-os/.claude/skills/test-backend Skill

    no license0★ repo

    Write, review, and audit backend tests for a Java codebase. Applies ISTQB CTFL v4.0 standards (black-box/white-box techniques, test pyramid, risk-based prioritization, defect taxonomy) with JUnit 5, Mockito, Spring Boot Test, and REST Assured. Triggers on "write tests for this service", "test this endpoint", "unit test", "integration test", "mock this repository", "test coverage Java", or any request to test Java backend code.

  • Test frontend

    talgacapri/pm-os/.claude/skills/test-frontend Skill

    no license0★ repo

    Write, review, and audit frontend tests for a React + Vitest + Playwright codebase. Applies ISTQB CTFL v4.0 standards (black-box techniques, test pyramid, risk-based prioritization, defect taxonomy) combined with E2E-first philosophy and AAA structure. Triggers on "write tests", "test this component", "test coverage", "Playwright", "Vitest", "RTL", "E2E for", or any request to write or review React/frontend tests.

  • Scaffold integration project

    jzills/claude-marketplace/plugins/dotnet-integration-tests/skills/scaffold-integration-project Skill

    no license0★ repo

    Use this skill when the user wants to create a new .NET integration test project from scratch. Trigger on: "create integration test project", "scaffold integration tests", "set up integration test project", "add integration tests to my solution", "create a test project for integration tests", "I don't have an integration test project yet", "bootstrap integration test infrastructure".

  • Setup test infrastructure

    jzills/claude-marketplace/plugins/dotnet-integration-tests/skills/setup-test-infrastructure Skill

    no license0★ repo

    Use this skill when the user wants to configure containers or Docker infrastructure for .NET integration tests. Trigger on: "set up containers for my tests", "configure docker for integration tests", "add testcontainers", "generate docker-compose for my tests", "set up test infrastructure", "what containers do I need", "configure test dependencies". Also invoked as a sub-skill when scaffolding a new integration test project.

  • Write integration tests

    jzills/claude-marketplace/plugins/dotnet-integration-tests/skills/write-integration-tests Skill

    no license0★ repo

    Use this skill whenever the user asks to write, generate, or add integration tests for C# or .NET code. Trigger on: "write integration tests", "add integration tests", "test this endpoint", "test this API", "integration test for this controller", "test against the database", "write end-to-end tests", "test this repository with a real database", "add integration test coverage". Also trigger when the user shows a controller, repository, or service and asks for tests that require real infrastructure (database, message broker, HTTP, etc.) rather than mocks.

  • Dotnet unit tests

    jzills/claude-marketplace/plugins/dotnet-unit-tests/skills/dotnet-unit-tests Skill

    no license0★ repo

    Use this skill whenever the user asks you to write, generate, add, or scaffold unit tests for C# or .NET code. Trigger on: "write tests for this", "add unit tests", "test this class", "generate tests", "cover this with tests", "write NUnit tests", "mock this dependency", "how do I test this", "add test coverage", "write a test for this method", or any request that involves C#/.NET testing. Also trigger proactively when the user shows you a C# class or method and asks you to improve, review, or complete it — if there are no tests, offer to write them.

  • Dependency upgrade

    mickzijdel/dev-hooks/plugins/dev-hooks/skills/dependency-upgrade Skill

    0★ repo

    Bring a repo's dependencies up to the latest versions across JavaScript (npm/pnpm/yarn), Ruby (bundler), Python (uv/poetry/pip), and GitHub Actions — reading changelogs/migration guides for major bumps, applying the needed code changes, and landing each step as its own verified commit. Use when the user wants to "update my packages", "upgrade dependencies", "bump deps to latest", "check for outdated packages", or do this across all their repos (fleet mode). Gates every commit on a green test suite; defers any major it can't get green to a written report. Pairs with the github-actions skill (Actions pins) and respects dev-env-setup's 4-day dependency cooldown.

  • Cicd fix deploy

    Methasit-Pun/ts-ddd-clean-architecture/skills/cicd-fix-deploy Skill

    0★ repo

    CI/CD specialist for TypeScript DDD projects on GitHub Actions. Use this skill whenever: a GitHub Actions workflow is failing or missing; `tsc` reports type errors in CI; Vitest tests are red in the pipeline; the user wants to verify the project is ready to deploy or merge; or any combination of "CI is broken", "types are failing", "tests won't pass", "fix the pipeline", "deploy ready", "prepare for production", "make CI green". Covers scaffolding missing workflow files, diagnosing and fixing TypeScript errors, diagnosing and fixing Vitest failures, and running a pre-deploy readiness gate. Always invoke before touching any .yml, tsconfig, or test file in a CI context.

    The same file is in 1 other repository

  • Tdd domain layer

    Methasit-Pun/ts-ddd-clean-architecture/skills/tdd-domain-layer Skill

    0★ repo

    Strict TDD for Domain and Application layers in Clean Architecture TypeScript. Red-Green-Refactor with Vitest. Mocks ports, never hits a database.

  • Nts testing patterns

    juncoding/nextjs-trpc-prisma-starter/skills/nts-testing-patterns Skill

    0★ repo

    Test-writing patterns for projects scaffolded with nextjs-trpc-prisma-starter. Use whenever the user is writing or reviewing tests in such a project, asks 'how do I test X', wants to add test coverage for a new module, or needs to debug a failing test. Covers service-layer unit tests (the high-value layer), tRPC procedure tests via createCaller (typed, no HTTP), MCP tool tests, route handler tests, and Playwright e2e. Each section explains WHAT to test at that layer and HOW so test effort lands where it pays off.

  • Testing

    Shankulkarni/RN-Lib-Claude/plugins/rn-lib-claude/skills/testing Skill

    no license0★ repo

    Use when writing tests for a React Native library — Jest setup with jest-expo preset, React Native Testing Library patterns, Reanimated mocks, Codegen mocks, what to test and what not to.

  • Code edges

    GRIDLOCK-NYC/claude-skills/skills/code-edges Skill

    0★ repo

    Audit a project for edge cases, error-prone code paths, and unhandled failure modes. Researches the codebase, identifies the highest-risk areas, enumerates specific edge cases from a comprehensive catalog, writes and runs tests to prove them, then produces a prioritized risk report. Use when user says 'edge audit', 'find edge cases', 'what could break', 'edge case review', 'audit for edge cases', 'stress test this code', 'what am I missing', 'failure modes', 'where will this break', 'robustness check', or 'error path audit'. Do NOT use for security scanning or dead code detection (use code-security for that). Do NOT use for code quality review of specific PRs (use code-review for that). Do NOT use for running existing test suites (use code-preflight for that).

  • Test driven development

    fabioc-aloha/Alex_ACT_Edition/.github/skills/test-driven-development Skill

    0★ repo

    Use for any feature, bug fix, refactor, or behavior change — enforces RED-GREEN-REFACTOR. Write the failing test first, watch it fail, write minimal code to pass, refactor. Carve out only throwaway prototypes, generated code, configuration files. Adapted from Hermes Agent / obra/superpowers.

  • Testing

    felixhennequin-gif/claude-code-config-template/.claude/skills/core/testing Skill

    0★ repo

    Testing strategy and conventions. Activates when writing tests, deciding what to test, editing files under *.test.*, *.spec.*, tests/, or __tests__/, setting up a test suite, or evaluating test coverage for any language or stack.

  • Testing

    felixhennequin-gif/claude-code-config-template/cli/template-files/claude/skills/core/testing Skill

    0★ repo

    Testing strategy and conventions. Activates when writing tests, deciding what to test, editing files under *.test.*, *.spec.*, tests/, or __tests__/, setting up a test suite, or evaluating test coverage for any language or stack.

  • Nfs testing patterns

    juncoding/nextjs-fullstack-starter/skills/nfs-testing-patterns Skill

    0★ repo

    Test-writing patterns for projects scaffolded with nextjs-fullstack-starter. Use whenever the user is writing or reviewing tests in such a project, asks 'how do I test X', wants to add test coverage for a new module, or needs to debug a failing test. Covers service-layer unit tests (the high-value layer where most coverage lives), integration tests with a real Postgres (Testcontainers), Server Action tests via direct invocation, route-handler tests, and Playwright e2e. Each section explains WHAT to test at that layer and HOW so test effort lands where it pays off.

  • Effect ts testing

    marzun9620/agent_skills/effect-ts/skills/effect-ts-testing Skill

    no license0★ repo

    This skill should be used when the user asks about "Effect testing", "@effect/vitest", "it.effect", "it.live", "it.scoped", "it.layer", "it.prop", "Schema Arbitrary", "property-based testing", "fast-check", "TestClock", "testing effects", "mocking services", "test layers", "TestContext", "Effect.provide test", "time testing", "Effect test utilities", "unit testing Effect", "generating test data", "flakyTest", "test coverage", "100% coverage", "service testing", "test doubles", "mock services", or needs to understand how to test Effect-based code.

  • Playwright cli

    marzun9620/agent_skills/testing/skills/playwright-cli Skill

    no license0★ repo

    Use when running Playwright via terminal CLI — `npx playwright test` (test runner), `codegen` (interactive recording), `screenshot` / `pdf` (one-off captures), and CI sharding. NOT for agent-driven real-time browser control (use `claude-in-chrome` MCP tools for that).

  • Playwright patterns

    marzun9620/agent_skills/testing/skills/playwright-patterns Skill

    no license0★ repo

    Patterns for writing Playwright E2E tests — POM structure, selector hierarchy, flow specs, waits, role contexts, dialog handling. Use when authoring or reviewing anything under /e2e.

  • Playwright test

    marzun9620/agent_skills/testing/skills/playwright-test Skill

    no license0★ repo

    Playwright Test (E2E) best practices and reference. Covers test authoring, avoiding fixed waits, network triggers, drag-and-drop, and shard/retry configuration in GitHub Actions. Use when writing, reviewing, or setting up CI for Playwright tests.

  • Tdd

    marzun9620/agent_skills/testing/skills/tdd Skill

    no license0★ repo

    Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

    The same file is in 17 other repositories

  • Workflow test factory

    marzun9620/agent_skills/workflow/skills/workflow-test-factory Skill

    no license0★ repo

    Test Factory authoring guide — Factory pattern for inserting rows into the database. Used in Drizzle ORM + Vitest environments. Triggers: Factory creation, test data, test helper, EntityFactory, create, build, test fixture.

  • React testing

    BTN101/claude-skill-pack/skills/engineering/react-testing Skill

    0★ repo

    React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress end-to-end runs. Use when writing or fixing tests for React components, hooks, or pages.

    The same file is in 1 other repository

  • Tdd workflow

    BTN101/claude-skill-pack/skills/engineering/tdd-workflow Skill

    0★ repo

    Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.

    The same file is in 8 other repositories

  • Engineering layer

    BTN101/claude-skill-pack/skills/layers/engineering-layer Skill

    0★ repo

    Activate this skill group for any technical, coding, or architecture task. Triggers include: building an API, designing endpoints, backend architecture, database schema, SQL queries, Postgres, migrations, React component, Next.js, Zustand state, Tailwind, shadcn, authentication, security checklist, JWT, input validation, secrets, deployment, Vercel, CI/CD, Docker, Java code, test-driven development, unit tests, React testing, performance optimization, memoization, code splitting, and any request where the primary deliverable is working code or a technical architecture decision. Use this skill group whenever Seb is building, debugging, or architecting anything for Antibody, SchoolOrder, or his GitHub portfolio.

  • Hv qa

    l4ci/hv-skills/hv-qa Skill

    0★ repo

    QA the built product — not the diff. Use on "/hv-qa", "run QA", "test the feature", "validate the build", before ship as a gate, or on first cycle to scaffold a per-repo strategy. Detects testing surfaces per repo (web, API, CLI, mobile, lib), picks runners (Playwright, smoke, contract, lighthouse, ZAP, axe), and produces a scored report with executable pass/fail results plus audit-style usability findings. Strategy is per-repo in .hv/qa/<repo>.md so the skill never hardcodes "browser". Modes — first-run (probe + propose strategy), run (execute strategy, emit verdict), restructure (audit strategy files). Opt-in gate via ship.qa.

  • Thrunt add tests

    3dcom2711/thrunt-god/thrunt-god/examples/brute-force-to-persistence/.github/skills/thrunt-add-tests Skill

    0★ repo

    Generate tests for a completed phase based on Evidence Review criteria and implementation

    The same file is in 1 other repository

  • Tdd expert

    SkillMedev/engineering-workflow/skills/tdd-expert Skill

    0★ repo

    Drive development with strict Red-Green-Refactor discipline - write one failing test, write the minimum code to pass it, refactor on green - including test-list planning and a worked kata cycle. Use when someone asks "write this test-first", "do TDD on this feature", "help me practice red-green-refactor", "write a failing test for this bug", or wants tests to drive a new module's design. Do NOT use for adding tests to existing untested legacy code before a refactor - use characterization-test-writer instead - or for designing shared fixtures and factories - use test-data-builder instead.

    The same file is in 3 other repositories

  • Ship demo

    taskmasterpeace/ship-pack/skills/ship-demo Skill

    0★ repo

    Generates realistic, obviously-fake demo/seed data plus a guided live-demo script for any project. Discovers the data model (Drizzle, Prisma, raw SQL/Supabase, TypeORM, Sequelize, Mongoose, or TS types), writes an idempotent seed script that builds a few complete, wired-up "hero" records, and writes docs/demo/script.md — a step-by-step walkthrough that hits the best features in a sensible order with what-to-say and what-to-show — then renders it to a themed presenter page. Use when the user wants demo data, seed data, sample/test/fixture data, a demo environment, a sales or investor demo, a demo script, a walkthrough, a guided product tour, a "fill the app with data" task, or to prep a live demo. Triggers on "seed the database", "demo data", "demo script", "walkthrough", "prep for a demo", "sample data", "populate the app".

  • Ab testing

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/ab-testing Skill

    0★ repo

    When to activate: A/B testing, split testing, experiment design, statistical significance, sample size, ICE framework, multivariate testing, conversion experiments

  • Beta testing

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/beta-testing Skill

    0★ repo

    When to activate: beta testing, beta program, beta users, closed beta, open beta, beta feedback, early access, beta-to-GA, launch criteria, beta metrics

  • Cpp testing

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/cpp-testing Skill

    0★ repo

    When to activate: C++ testing, Google Test, GTest, GMock, Catch2, doctest, fixtures, parameterized tests, benchmarks, mocking

  • Data analysis

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/data-analysis Skill

    0★ repo

    When to activate: data analysis, statistical analysis, hypothesis testing, A/B test analysis, regression, data visualization, insight generation, descriptive statistics, inferential statistics

  • Discovery frameworks

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/discovery-frameworks Skill

    0★ repo

    When to activate: product discovery, continuous discovery, opportunity solution tree, assumption testing, Teresa Torres, experiment design, fake door test, concierge test

  • Flutter testing

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/flutter-testing Skill

    0★ repo

    When to activate: Flutter testing, widget tests, unit tests, integration tests, mockito, golden tests, pump, pumpWidget, WidgetTester

  • Golang testing

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/golang-testing Skill

    0★ repo

    When to activate: Go tests, table-driven tests, testify, mocks, subtests, benchmarks, fuzz testing, test helpers

  • Java testing

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/java-testing Skill

    0★ repo

    When to activate: Java testing, JUnit 5, Mockito, AssertJ, Testcontainers, WireMock, Spring MVC test, parameterized tests

  • Kotlin testing

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/kotlin-testing Skill

    0★ repo

    When to activate: Kotlin testing, JUnit 5, Kotest, MockK, Testcontainers, coroutine testing, Spring test slices, runTest

  • Pytest advanced

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/pytest-advanced Skill

    0★ repo

    When to activate: pytest plugins, conftest, custom markers, test architecture, fixtures design, pytest-xdist, coverage strategies

  • Python testing

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/python-testing Skill

    0★ repo

    When to activate: pytest, TDD, test fixtures, parametrize, async tests, coverage, mocking, hypothesis

  • React testing

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/react-testing Skill

    0★ repo

    When to activate: React Testing Library, vitest, jest, component tests, user-event, MSW, accessibility queries, async testing

  • Rust testing

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/rust-testing Skill

    0★ repo

    When to activate: Rust tests, unit tests, integration tests, doc tests, benchmarks, proptest, test helpers, test organization

  • Swift testing

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/swift-testing Skill

    0★ repo

    When to activate: Swift Testing framework, XCTest, unit tests, async tests, test macros, parameterized tests, Swift mocking

  • Testing patterns

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/testing-patterns Skill

    0★ repo

    When to activate: Vitest, Testing Library, MSW, Playwright, visual regression, a11y testing, component tests, E2E tests

  • Hhh dialect verify report

    Srltas/claude-skills/hhh-dialect-verify-report Skill

    0★ repo

    One-shot CUBRID dialect verification + report. Runs the hibernate-core test suite against one or ALL CUBRID versions, diffs pass/fail vs a baseline (a prior run's JSON, results dir, or .tgz), and ALWAYS produces a Korean Word (.docx) 비교 분석 report. Use when you want the full 'verify → measure → report' pipeline for a CUBRIDDialect change in one go, or to test across all CUBRID versions. Composes the hhh-dialect-verify and report skills. Triggers on phrases like 'dialect 검증하고 리포트까지', 'CUBRID 전체 버전 테스트 + 보고서', 'verify the dialect and write the report', 'run all CUBRID versions and report'.

  • Hhh dialect verify

    Srltas/claude-skills/hhh-dialect-verify Skill

    0★ repo

    Run the Hibernate ORM test suite against CUBRID and measure a dialect change's impact: total failures, +N recovered / −N regressed vs a baseline, and failures grouped by signature/family. Use when verifying a CUBRIDDialect change, an auto_quote or capability-flag toggle, or any Hibernate-vs-CUBRID compatibility measurement. Pairs with the report skill (verify → numbers → 비교 분석 보고서). Triggers on phrases like 'dialect 검증', 'CUBRID 테스트 돌려', 'hibernate 스위트 실행', 'pass/fail 델타 측정', 'run the hibernate suite against CUBRID', 'measure dialect change'.