skills.rest
ZaxbyHub
ZaxbyHubOFFICIAL
Explore all skills by this author →
GitHub

propagation-test

Verify shared module updates across all dependent consumer components.

437|45|Updated Jan 27, 2026
Search Tags:#code review#test coverage#software testing#shared module#propagation test#single-source update#consumer validation
One-click install
npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill propagation-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: propagation-test
Source: https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/generated/propagation-test
Command: npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill propagation-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of undetected breakage in dependent components when updating shared modules, ensuring all consumers remain functional after single-source changes.

Core Features & Use Cases

  • Propagation Testing Enforcement: Requires testing all consumers via the shared module's public seam, preventing patchwork fixes to individual consumer internals.
  • Built-in Quality Checks: Includes dedicated reviewer and test engineer checklists to validate propagation coverage and test completeness.
  • Use Case: When updating a shared authentication utility used by 4 different microservices, use this Skill to confirm the update works across all services without modifying each service's internal code.

Quick Start

Use the propagation-test skill to verify that your recent shared module update functions correctly for all dependent consumer components.

Frequently Asked Questions about propagation-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is propagation testing for shared module updates?▼

Propagation testing validates shared module updates by exercising all consumer services via the module's public seam to ensure dependent components remain functional without modifying their internal implementations.

How do I test shared library updates across multiple consumer services?▼

Test shared library updates by requiring coverage that exercises all consumers via the shared module's public seam, enforcing single-source validation rather than applying patchwork fixes to individual consumer internal implementations.

Why does updating a shared utility break dependent microservices?▼

Shared utility updates break dependent microservices when test coverage lacks consumer validation, failing to exercise all consumers via the public seam and leaving undetected breakage in dependent components.

Can I validate a single-source update without modifying individual consumer internals?▼

Yes, you can validate single-source updates by testing all consumers through the shared module's public seam, which confirms functionality across dependent services without requiring modifications to their internal code.

What's the best way to prevent undetected breakage in dependent components?▼

Prevent undetected breakage by enforcing propagation testing with dedicated reviewer and test engineer checklists, validating that test coverage exercises all consumers via the shared module's public seam.

Related Skills

Explore More Software Engineering Skills→
Pact-Community-OrganizationPact-Community-Organization
1

test-coverage-analysis

Map Pact module public functions to tests and prioritize coverage gaps.

Official
Intermediate
EojEdredEojEdred

runtime-dev01

Monitor validator runtime performance and coordinate upgrades for Ëtrid.

Community
Intermediate
mvillmowmvillmow
18

calculate-coverage

Calculate code coverage percentages and identify uncovered lines and branches.

Community
Intermediate
rnavarychrnavarych
14

contract-testing

Verify microservice API contracts with Pact consumer-driven testing.

Community
Advanced