@c8y/client Migration Analysis Methodology

Audit Cumulocity Angular codebases for @c8y/client breaking changes during Web SDK upgrades.

5|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/Cumulocity-IoT/cumulocity-skills --skill c8y-client-migration-analysis-methodology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: @c8y/client Migration Analysis Methodology
Source: https://github.com/Cumulocity-IoT/cumulocity-skills/tree/main/skills/c8y-client-migration-analysis
Command: npx skills add https://github.com/Cumulocity-IoT/cumulocity-skills --skill c8y-client-migration-analysis-methodology

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a structured, step-by-step methodology to audit a Cumulocity Angular codebase for Web SDK version upgrades, preventing incorrect assumptions and wasted effort.

Core Features & Use Cases

  • Systematic Audit Process: Guides users through reading changelogs, mapping service imports, cataloging method calls, and cross-checking against breaking changes.
  • Impact Classification: Helps categorize the impact of breaking changes as "Not applicable", "OK", "INFO", or "Action required".
  • Use Case: Before upgrading your Angular application from Web SDK 1021 to 1023, use this skill to systematically identify all @c8y/client service usages, understand the breaking changes, and determine which code modifications are truly necessary.

Quick Start

Use the c8y-client-migration-analysis skill to audit this project for a target Web SDK 1023 upgrade.

Frequently Asked Questions about @c8y/client Migration Analysis Methodology

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

FAQPage Schema
How do I audit a Cumulocity Angular codebase before a Web SDK upgrade?

To audit a Cumulocity Angular codebase for a Web SDK upgrade, systematically read breaking changelogs, build a service import map for @c8y/client, catalog method calls, and classify the impact of changes to estimate required actions.

What is the best way to analyze @c8y/client service usage for breaking changes?

Analyzing @c8y/client service usage involves mapping service imports, cataloging method calls across the project, and cross-referencing those calls against specific breaking changelog criteria to identify necessary code modifications.

How do I classify the impact of breaking changes during an Angular migration?

During Angular migration, classify the impact of breaking changes by verifying findings against specific criteria, categorizing each change as Not applicable, OK, INFO, or Action required to estimate required development effort.

When do I need a structured methodology for upgrading Cumulocity Web SDK versions?

A structured methodology is needed before upgrading Cumulocity Web SDK versions to prevent incorrect assumptions and wasted effort, ensuring systematic analysis of all @c8y/client service usages and breaking changes.

Can I use this audit process for upgrading from Web SDK 1021 to 1023?

Yes, you can use this audit process before upgrading from Web SDK 1021 to 1023 to systematically identify all @c8y/client service usages, understand breaking changes, and determine which code modifications are truly necessary.