branch-uml-diagrams

To generate PlantUML diagrams for code changes, this skill computes diffs against the merge-base with main, resolves corresponding spec files, and creates before/after diagrams for each modified file. It then validates PlantUML syntax to ensure diagrams render correctly.

Visualizing architecture shifts before a pull request is done by comparing your feature branch to the main merge-base. The skill identifies meaningful changes and outputs before/after PlantUML diagrams for relevant specs, enabling quick architectural review.

PlantUML diagrams are mapped to modified files using a spec-driver workflow. The skill computes the branch diff, resolves corresponding spec files located within specs folders, and generates the PlantUML files directly in those spec directories.

Yes, you can validate PlantUML syntax automatically during branch diff diagram generation. The skill includes a syntax validation step that checks the generated before and after PlantUML files to ensure they render correctly before review.

Automated UML generation works without manual spec file location inputs by using the spec-driver workflow. It automatically locates corresponding spec files within specs folders for each modified file detected from the branch diff.

Before and after PlantUML diagrams are needed to quickly highlight architectural changes. By comparing the merge-base with the feature branch, the diagrams clearly show the structural shifts triggered by code changes for quick review.