demoshop-integration

Integrate the latest upstream changes quickly and accurately with automated workflowsGitHub Actions Continuous Integration and Delivery for seamless DevOps integration and delivery.

6|13|Updated Feb 4, 2019
One-click install
npx skills add https://github.com/spryker-shop/b2b-demo-marketplace --skill demoshop-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: demoshop-integration
Source: https://github.com/spryker-shop/b2b-demo-marketplace/tree/main/.claude/skills/integration
Command: npx skills add https://github.com/spryker-shop/b2b-demo-marketplace --skill demoshop-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex process of integrating updates and project changes from the Spryker Suite repository into a Spryker Demoshop, saving significant development time and reducing manual errors.

Core Features & Use Cases

  • Automated Dependency Resolution: Identifies and updates spryker-feature/* packages via Composer.
  • Project-Level Change Application: Fetches and applies diffs from Spryker Suite pull requests.
  • Branch Management: Creates and manages integration branches with appropriate naming conventions.
  • Conflict Handling: Flags and documents conflicts for manual review.
  • PR Creation: Generates pull requests with detailed summaries and CI notices.
  • Use Case: A developer needs to integrate a new feature or a critical bug fix from the Spryker Suite into the b2b-marketplace Demoshop. This Skill guides them through updating composer packages, applying code changes from the Suite PR, and creating a new pull request for the Demoshop repository.

Quick Start

Use the demoshop-integration skill to integrate ticket ABC-1234 and apply project changes from the provided suite PR URL.

Frequently Asked Questions about demoshop-integration

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

FAQPage Schema
How do I automate Spryker package updates and apply changes to a demoshop?

To automate Spryker package updates, this workflow resolves dependencies via Composer and applies code diffs from GitHub pull requests directly into your demoshop, handling branch creation and pull request generation end-to-end.

What is the process for integrating Spryker Suite project-level changes into a demoshop?

Integrating Spryker Suite changes involves fetching diffs from the Suite repository pull requests, applying them to your demoshop codebase, resolving any flagged conflicts for manual review, and generating a summary pull request for the target repository.

Do I need the GitHub CLI to apply Spryker Suite code updates to my project?

Yes, you need the GitHub CLI (gh) installed and authenticated, as it is required for repository interactions including fetching pull request diffs, managing integration branches, and creating new pull requests during the update process.

How does this integration handle composer dependency resolution for Spryker features?

Dependency resolution automatically identifies and updates spryker-feature/* packages via Composer, ensuring your demoshop's required Spryker Suite feature packages are correctly synchronized before project-level code changes are applied.

What happens when there are code conflicts while applying Spryker Suite pull request diffs?

When code conflicts occur while applying pull request diffs, the integration workflow flags and documents these conflicts specifically for manual review, allowing you to resolve them safely without breaking the automated integration branch.

Can I use this automation to integrate a critical bug fix from a Suite PR into the b2b-marketplace demoshop?

Yes, you can use this automation to integrate features or bug fixes from a Spryker Suite PR into the b2b-marketplace demoshop by updating composer packages, applying the suite PR code changes, and generating a new demoshop pull request.