Umbraco.Automate: Skill for Claude Code

Release Manager

You are the orchestrator for preparing releases in the Umbraco.Automate repository.

Task

Guide users through the complete release preparation process:

1. Detect changed products since their last release tags
2. Analyze commits to recommend version bumps (major/minor/patch)
3. Cascade forced bumps to every dependent of a product undergoing minor/major/downplayed-breaking changes
4. Confirm versions with the user (including cascaded products)
5. Update Directory.Packages.props inter-product dependency ranges (with user approval)
6. Create release branch (e.g., v18/release/2026.02.1) and switch to it
7. Dependency validation - Check for cross-product conflicts using the graph built in cascade analysis
8. Update version.json files for each product
9. Generate release-manifest.json via /release-manifest-management
10. Generate CHANGELOG.md files via /changelog-management
11. Changelog review - Review generated changelogs for quality and completeness
12. Validate all files are consistent
13. Commit all changes to the release branch

Workflow

Phase 1: Change Detection

1. Find all products - Discover Umbraco.Automate* directories at repo root

2. For each product, detect changes since last release:

   # Find the most recent release tag for this product that is REACHABLE from HEAD.
   # Use git describe (reachability-based), NOT `git tag --list --sort=-version:refname`
   # (version-sorted). On parallel support lines (e.g. support/17.x alongside an 18.x
   # line on dev/main), a version sort would pick the highest tag across ALL branches —
   # so a 17.x release run would wrongly grab an 18.x tag as its base. git describe walks
   # back from HEAD and only sees tags on this line's history. This matches CI's
   # detect-changes.ps1 (`git describe --tags --abbrev=0 --match=...`), so the skill and
   # CI agree on each product's base tag.
   git describe --tags --abbrev=0 --match="<Product>@*"   # e.g. --match="Umbraco.Automate@*"
   # Exit code != 0 means no matching tag is reachable (first release on this line) —
   # fall back to merge-base with this line's vN/main (see Error Handling).
   
   # Get commits affecting this product since that tag
   git log <tag>..HEAD --oneline -- <ProductFolder>/
   
   # Exclude non-substantive changes (CHANGELOG.md, version.json)
   git diff <tag>..HEAD --name-only -- <ProductFolder>/ | grep -v 'CHANGELOG.md\|version.json'