[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ARP15D08HAXZ67P276MQRF":3,"skill-same:01M7ARP15D08HAXZ67P276MQRF":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7ARP15D08HAXZ67P276MQRF","contract-testing",null,"Sets up consumer-driven contract tests for APIs and events: provider verification, provider states, a broker, can-I-deploy checks and schema compatibility. Use when the user says 'contract test' or asks 'will this API change break clients'. Not for deep tests of one API (use api-testing).","quark-sri\u002Fqestack","quark-sri","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F89900424?v=4","01M7ARN6E370E8C9T165BKJB5G","Srinivas Pasupulati","01M7ARN6F6BCMFYCV5RC5HR9JC",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fquark-sri\u002Fqestack\u002Fblob\u002Fmain\u002Fplugins\u002Fqestack\u002Fskills\u002Fcontract-testing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: contract-testing\ndescription: \"Sets up consumer-driven contract tests for APIs and events: provider verification, provider states, a broker, can-I-deploy checks and schema compatibility. Use when the user says 'contract test' or asks 'will this API change break clients'. Not for deep tests of one API (use api-testing).\"\nlicense: Apache-2.0\nargument-hint: \"[consumer, provider or interface]\"\n---\n\n# contract-testing\n\n## Objective\n\nEnd-to-end tests between services are slow and fragile, and they find breaking changes late. A contract test checks the agreement between two parties in isolation: the consumer states what it needs, and the provider proves that it delivers it. The pipeline can then block a deploy that would break a consumer.\n\n## Context\n\n1. Read `.agents\u002Fqa-project-context.md` if it exists. Use its services, API styles, messaging and pipeline.\n2. If it does not exist, find the consumers and providers from the code, the configuration and the documentation. Suggest `qa-project-context` once. Do not stop the work for it.\n\n## Discovery questions\n\n1. Which services talk to which, over which interfaces (HTTP, events, RPC)? Which teams own them?\n2. Is there a contract tool or broker in use? Is there a schema registry for events?\n3. Who changes an interface first, and how do teams agree on changes today?\n\n## Principles\n\n1. **The consumer defines what it uses,** not the whole provider interface. Fields that no consumer uses can change freely.\n2. **Match on type and shape, not on exact data,** except where the consumer depends on a value.\n3. **Provider states** set up the data that each interaction needs. They are part of the contract.\n4. **Contracts are versioned and verified in the pipeline** of both sides. A deploy checks that the deployed versions are compatible.\n5. **Events need compatibility rules too:** a schema registry check (for example backward compatible) or event contracts.\n\n## Workflow\n\n1. Map the interactions in scope: consumer, provider, interface, owner.\n2. **Consumer side:** write a contract test for each interaction that the consumer uses. It describes the request (or the expected event) and the minimum response that the consumer needs, with type matchers. The test runs the consumer code against a mock provider that the tool creates from the contract.\n3. **Publish** the contract to the broker or the shared repository, with the consumer version and branch.\n4. **Provider side:** verify all relevant consumer contracts against the real provider (in process or a test instance), with provider states for the data.\n5. **Pipeline:** run the consumer tests and the provider verification on each change. Before a deploy, check that this version is compatible with the deployed versions of the other side.\n6. **Events:** register schemas, set the compatibility mode, and check compatibility in the pipeline before publishing a new version.\n\n## Stack recipes\n\nRead only the recipe for the stack of the project: [Java](references\u002Fjava.md), [TypeScript and JavaScript](references\u002Ftypescript.md), [Python](references\u002Fpython.md). For another stack, apply the principles with the project's own tools, and say so.\n\n## Anti-patterns\n\n- **The provider writes the consumer's contract.** It then tests what the provider thinks, not what the consumer needs.\n- **Exact data matching everywhere.** The contract breaks on harmless data changes.\n- **Contracts that never block a deploy.** Without the pipeline check, they are documentation.\n- **Contract tests as functional tests.** Business rules belong in the provider's own tests.\n\n## Done when\n\n- Each consumer-provider interaction in scope has a consumer contract with type matchers.\n- The provider verifies the contracts with provider states in its pipeline.\n- A deploy step checks compatibility with the deployed versions.\n- Event schemas have a compatibility rule that the pipeline checks.\n\n## Related skills\n\n- `api-testing`: the provider's behavior in depth.\n- `messaging-testing`: event producers and consumers.\n- `ci-cd-integration`: the verification and deploy checks.\n- `spec-drift`: drift between the contract, the docs and the code.\n","# contract-testing\n\n## Objective\n\nEnd-to-end tests between services are slow and fragile, and they find breaking changes late. A contract test checks the agreement between two parties in isolation: the consumer states what it needs, and the provider proves that it delivers it. The pipeline can then block a deploy that would break a consumer.\n\n## Context\n\n1. Read `.agents\u002Fqa-project-context.md` if it exists. Use its services, API styles, messaging and pipeline.\n2. If it does not exist, find the consumers and providers from the code, the configuration and the documentation. Suggest `qa-project-context` once. Do not stop the work for it.\n\n## Discovery questions\n\n1. Which services talk to which, over which interfaces (HTTP, events, RPC)? Which teams own them?\n2. Is there a contract tool or broker in use? Is there a schema registry for events?\n3. Who changes an interface first, and how do teams agree on changes today?\n\n## Principles\n\n1. **The consumer defines what it uses,** not the whole provider interface. Fields that no consumer uses can change freely.\n2. **Match on type and shape, not on exact data,** except where the consumer depends on a value.\n3. **Provider states** set up the data that each interaction needs. They are part of the contract.\n4. **Contracts are versioned and verified in the pipeline** of both sides. A deploy checks that the deployed versions are compatible.\n5. **Events need compatibility rules too:** a schema registry check (for example backward compatible) or event contracts.\n\n## Workflow\n\n1. Map the interactions in scope: consumer, provider, interface, owner.\n2. **Consumer side:** write a contract test for each interaction that the consumer uses. It describes the request (or the expected event) and the minimum response that the consumer needs, with type matchers. The test runs the consumer code against a mock provider that the tool creates from the contract.\n3. **Publish** the contract to the broker or the shared repository, with the consumer version and branch.\n4. **Provider side:** verify all relevant consumer contracts against the real provider (in process or a test instance), with provider states for the data.\n5. **Pipeline:** run the consumer tests and the provider verification on each change. Before a deploy, check that this version is compatible with the deployed versions of the other side.\n6. **Events:** register schemas, set the compatibility mode, and check compatibility in the pipeline before publishing a new version.\n\n## Stack recipes\n\nRead only the recipe for the stack of the project: [Java](references\u002Fjava.md), [TypeScript and JavaScript](references\u002Ftypescript.md), [Python](references\u002Fpython.md). For another stack, apply the principles with the project's own tools, and say so.\n\n## Anti-patterns\n\n- **The provider writes the consumer's contract.** It then tests what the provider thinks, not what the consumer needs.\n- **Exact data matching everywhere.** The contract breaks on harmless data changes.\n- **Contracts that never block a deploy.** Without the pipeline check, they are documentation.\n- **Contract tests as functional tests.** Business rules belong in the provider's own tests.\n\n## Done when\n\n- Each consumer-provider interaction in scope has a consumer contract with type matchers.\n- The provider verifies the contracts with provider states in its pipeline.\n- A deploy step checks compatibility with the deployed versions.\n- Event schemas have a compatibility rule that the pipeline checks.\n\n## Related skills\n\n- `api-testing`: the provider's behavior in depth.\n- `messaging-testing`: event producers and consumers.\n- `ci-cd-integration`: the verification and deploy checks.\n- `spec-drift`: drift between the contract, the docs and the code.\n",{"name":5,"license":15,"description":7,"argument-hint":24},"[consumer, provider or interface]","main","33cd1b197739d1c9a7a907bc4bb50c00039c2371","plugins\u002Fqestack\u002Fskills\u002Fcontract-testing",0,"https:\u002F\u002Fgithub.com\u002Fquark-sri\u002Fqestack","https:\u002F\u002Fgithub.com\u002Fquark-sri","2026-11-14 20:45:02",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add quark-sri\u002Fqestack --skill contract-testing",{"tool":38,"command":39},"bunx","bunx skills add quark-sri\u002Fqestack --skill contract-testing",{"tool":41,"command":42},"pnpm","pnpm dlx skills add quark-sri\u002Fqestack --skill contract-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fquark-sri\u002Fqestack\u002Fblob\u002Fmain\u002Fplugins\u002Fqestack\u002Fskills\u002Fcontract-testing\u002FSKILL.md",true,[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fjava.md","REFERENCE","参考文档",2091,"https:\u002F\u002Fgithub.com\u002Fquark-sri\u002Fqestack\u002Fblob\u002Fmain\u002Fplugins\u002Fqestack\u002Fskills\u002Fcontract-testing\u002Freferences\u002Fjava.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fpython.md",1213,"https:\u002F\u002Fgithub.com\u002Fquark-sri\u002Fqestack\u002Fblob\u002Fmain\u002Fplugins\u002Fqestack\u002Fskills\u002Fcontract-testing\u002Freferences\u002Fpython.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Ftypescript.md",1407,"https:\u002F\u002Fgithub.com\u002Fquark-sri\u002Fqestack\u002Fblob\u002Fmain\u002Fplugins\u002Fqestack\u002Fskills\u002Fcontract-testing\u002Freferences\u002Ftypescript.md",[61,68,75,82,89,96],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7ARWD0Z563VXR17R8QMHWKE","unit-testing","Writes, fixes or improves unit tests for rules, calculations, validation and state logic: arrange-act-assert, exact oracles, boundary sets, doubles only at boundaries, controlled clock and randomness. Use when the user says 'write unit tests', 'TDD this' or 'mock this dependency'. Not for HTTP endpoints (use api-testing).","https:\u002F\u002Fgithub.com\u002Fquark-sri\u002Fqestack\u002Fblob\u002Fmain\u002Fplugins\u002Fqestack\u002Fskills\u002Funit-testing\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7ARW7HQKKAWQZ4K8128SBXC","ui-automation","Writes, fixes or structures browser end-to-end tests for critical journeys: role, label or test ID locators, auto-waiting assertions, API data setup, page objects, auth reuse and traces. Use when the user says 'UI test', 'end-to-end test' or 'our UI tests are brittle'. Not for business rules (use unit-testing).","https:\u002F\u002Fgithub.com\u002Fquark-sri\u002Fqestack\u002Fblob\u002Fmain\u002Fplugins\u002Fqestack\u002Fskills\u002Fui-automation\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7ARW22645WR7R6MKTAP1CVP","testcase-reviewer","Reviews automated tests or manual test cases like a senior test architect: scores fidelity, oracles, assertion depth, edge cases and determinism, and finds tests that pass on wrong code. Use when the user says 'review my tests', 'test smells' or 'review AI-written tests'. Not for fault injection (use mutation-probe).","https:\u002F\u002Fgithub.com\u002Fquark-sri\u002Fqestack\u002Fblob\u002Fmain\u002Fplugins\u002Fqestack\u002Fskills\u002Ftestcase-reviewer\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7ARVXYW0WTC5E7J5CR4S0EC","testability-review","Scores how testable a feature, module or design is before tests exist (seams for clock, randomness and network, hidden state, observability) and gives the smallest production change per blocker. Use when the user asks 'is this testable' or 'why is this hard to test'. Not for writing the tests (use unit-testing).","https:\u002F\u002Fgithub.com\u002Fquark-sri\u002Fqestack\u002Fblob\u002Fmain\u002Fplugins\u002Fqestack\u002Fskills\u002Ftestability-review\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7ARVTENW2RDMMKHDTGMYQBM","test-strategy","Writes a test strategy for a product, system or team: quality goals, test levels and their share, environments, data, automation scope, non-functional testing, metrics and a roadmap. Use when the user says 'test strategy' or 'QA strategy'. Not for one sprint or release plan (use test-planning).","https:\u002F\u002Fgithub.com\u002Fquark-sri\u002Fqestack\u002Fblob\u002Fmain\u002Fplugins\u002Fqestack\u002Fskills\u002Ftest-strategy\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7ARVMXVKN1XHB1QQCRNGXP5","test-runner","Finds how a project runs its tests, runs the right subset, and triages each failure as product bug, test defect, environment problem or flaky test, with evidence. Use when the user says 'run the tests' or asks 'which tests fail and why'. Not for pipeline design (use ci-cd-integration).","https:\u002F\u002Fgithub.com\u002Fquark-sri\u002Fqestack\u002Fblob\u002Fmain\u002Fplugins\u002Fqestack\u002Fskills\u002Ftest-runner\u002FSKILL.md",[],[]]