ecm-model-diff-summarizer

Name: ecm-model-diff-summarizer
Availability: InStock
Author: thomasrohde

Compare two ECM model Git refs and summarize capability-model differences by category.

1|Updated Apr 25, 2026

Search Tags:#git #diff #branch #summary #risk #capability-model

Ready to run

npx skills add https://github.com/ThomasRohde/ecm-studio --skill ecm-model-diff-summarizer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ecm-model-diff-summarizer
Source: https://github.com/ThomasRohde/ecm-studio/tree/main/.agents/skills/ecm-model-diff-summarizer
Command: npx skills add https://github.com/ThomasRohde/ecm-studio --skill ecm-model-diff-summarizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a business-readable summary of differences between two ECM Studio capability-model git refs, including added, removed, renamed, moved, retired, lifecycle-changed, metadata-changed, and type-transitioned capabilities, to support branch reviews, release notes, and scenario comparisons.

Core Features & Use Cases

Summarizes change counts by category (added, removed, renamed, moved, retired, lifecycle-changed, metadata-changed, type-transitioned).
Lists material changes by category and highlights risky changes such as removals or moves.
Facilitates quick, human-readable diffs for decision-making during reviews and planning.

Quick Start

Run a diff between two git refs in your ECM model repository to generate a concise, business-oriented capability-model summary.

Frequently Asked Questions about ecm-model-diff-summarizer

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

FAQPage Schema

How do I summarize ECM capability-model differences between two git branches?▼

You can summarize capability-model differences by comparing two git refs in your repository. The tool categorizes changes like added, removed, renamed, and moved capabilities, then counts occurrences to generate a concise summary for branch reviews and release notes.

What types of capability-model changes are tracked in an ECM git diff summary?▼

The diff summary tracks added, removed, renamed, moved, retired, lifecycle-changed, metadata-changed, and type-transitioned capabilities. It categorizes these changes and counts occurrences to highlight risky modifications such as removals or moves for review planning.

Can I generate release notes from ECM Studio capability-model git refs?▼

Yes, you can generate release notes by running a diff between two ECM Studio capability-model git refs. The summary categorizes and counts capability changes, providing a human-readable overview of material modifications for release documentation.

Do both git refs need to exist in the repository to compare ECM models?▼

Yes, both git refs must exist in the repository to compare ECM models. The diff summarizer requires two valid refs to identify capability-model differences and relies on an existing diff tool to produce the change summary.

What is the best way to review risky capability-model changes before a release?▼

The best way to review risky changes is to generate a diff summary between two git refs. The summary highlights risky modifications like removals and moves, categorizing all changes to facilitate quick decision-making during reviews and planning.