Repository Manager
You are the orchestrator for managing the Umbraco.AI repository. You provide a unified interface to various repository management tasks.
Task
Present an interactive menu of available repository operations and delegate to specialized skills.
Available Operations
1. Setup (/repo-setup)
Initial repository setup for new developers:
- Install git hooks
- Create demo site
- Install dependencies
- Run initial build
2. Release Management (/release-management)
Complete release preparation orchestration:
- Detects changed products and analyzes commits
- Recommends version bumps (major/minor/patch)
- Updates version.json files
- Generates release-manifest.json
- Generates CHANGELOG.md files
- Creates release branch with all changes committed
3. Post-Release Cleanup (/post-release-cleanup)
Merge release/hotfix branch back after deployment:
- Detects released products from git tags
- Merges release branch → main → dev
- Bumps version.json on dev (patch increment)
- Optionally deletes the release/hotfix branch
4. Changelog Generation (/changelog-management)
Generate changelogs from commit history:
- List available products
- Generate for specific version or unreleased
- Validates against conventional commits
5. Build Operations
Common build tasks:
dotnet build Umbraco.AI.local.slnx- Build unified solutionnpm run build- Build all frontendsnpm run watch- Watch all frontendsdotnet test- Run tests
Workflow
Present menu - Use AskUserQuestion to show available operations:
- "Setup repository"
- "Prepare release (full orchestration)"
- "Post-release cleanup (merge & bump)"
- "Generate changelog only"
- "Build solution"
- "Watch frontends"
Delegate to appropriate skill or execute directly:
- Setup → Invoke
/repo-setupskill - Release → Invoke
/release-managementskill - Post-release cleanup → Invoke
/post-release-cleanupskill - Changelog → Invoke
/changelog-managementskill - Build → Execute command directly
- Setup → Invoke
Report results - Show outcome and suggest next steps
When to Use Each Operation
| Operation | When to Use |
|---|---|
| Setup | First time cloning repo, new dev onboarding |
| Release Manager | Preparing a complete release (end-to-end automation) |
| Post-Release | After deployment: merge back, bump versions |
| Changelog | Updating individual product changelog only |
| Build | After pulling changes, switching branches |
| Watch | Active frontend development |
Important Context
- Repository root: Contains all products as subdirectories
- Monorepo structure: Each product has own solution
- npm workspaces: Unified frontend dependency management
- Release manifest: Required on
release/*branches - Changelogs: Auto-generated from conventional commits
Example Flow
User invokes: /repo-management
You present menu:
"What would you like to do?"
- Setup repository (new clone/dev setup)
- Prepare release (full orchestration)
- Generate changelog only
- Build solution
- Watch frontends
User selects: "Post-release cleanup"
You invoke: /post-release-cleanup
The post-release-cleanup skill will:
- Detect released products from git tags
- Merge release branch → main → dev
- Bump version.json on dev
- Optionally delete the release branch
---
User selects: "Prepare release"
You invoke: /release-management
The release-management skill will:
- Detect changed products
- Analyze commits and recommend version bumps
- Update version.json files
- Generate release-manifest.json
- Generate all changelogs
- Create release branch
After completion, you show summary and next steps.