Validate cross-boundary event contracts and propose a merge order for integration.
npx skills add https://github.com/tyevans/tackline --skill integrate-tyevans
Please help me install this Agent Skill. Skill: integrate Source: https://github.com/tyevans/tackline/tree/main/skills/workflows/integrate Command: npx skills add https://github.com/tyevans/tackline --skill integrate-tyevans
This Skill ensures that independently developed software components, designed around shared event contracts, can be safely integrated by verifying their adherence to those contracts and proposing a merge strategy.
/integrate to ensure all services correctly emit and consume events as defined, and to get a clear plan for merging their code.Use the integrate skill to validate contracts and propose a merge order for the contracts found in the 'event-contracts' directory.
High-intent search queries and answers about installing and using this skill.
Validating event contracts between bounded contexts requires checking each component's implementation against predefined event schemas to ensure provided and consumed events match. This process verifies compliance, detects semantic conflicts, and proposes a safe merge order for integration.
Merging independently developed components involves orchestrating contract compliance checks, cross-boundary event flow testing, and conflict detection. This generates an actionable merge proposal with specific conflict resolution steps for component branches.
Detecting orphan events and contract mismatches is accomplished through end-to-end event flow testing across bounded contexts. This cross-boundary testing validates that events flow correctly between components and surfaces structural mismatches in implementations.
Integrating microservices without predefined event schemas is not supported. Contract compliance checks require strict adherence to predefined schema formats and implementation patterns for bounded contexts to successfully verify cross-boundary contracts.
Cross-boundary event flow testing fails when independently developed software components do not adhere to defined event schemas. Structural and semantic conflicts in contracts and implementations cause mismatches, orphan events, and integration failures that block merging.
FoxSilouConvert event-storming documentation into screen inventories and presenter specifications.
ReinaMacCredyMerge origin/main into a local Git branch with guided conflict resolution.
arbazkhan971Model complex business domains into bounded contexts, aggregates, and event catalogs.
ksciusResolve Git merge conflicts and verify buildable, test-passing state.