ecm-model-diff-summarizer

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.

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.

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.

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.

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.