Covers the full release pipeline for the unifi-mcp monorepo: determining release scope by analyzing changed packages, scoping hatch-vcs version tag globs per Python package to prevent sibling-tag contamination, pushing tags in strict dependency order (unifi-core → unifi-mcp-shared → app servers → relay → worker when needed), configuring scripts/generate_release_notes.py path scoping per package, wiring per-package publish workflows for OIDC trusted publishing, coordinating cross-package version bumps in pyproject.toml, understanding app vs. library versioning and writeback behavior, validating releases post-tag, and verifying shared package architecture constraints (DI-only rule, scope gate, relay sync) before releasing shared packages. Apply when cutting any release, bumping unifi-core, or debugging a versioning failure. CRITICAL: All PRs require pin-alignment CI gate before merge (automated, cannot be skipped).
$npx -y skills add sirkirby/unifi-mcp --skill monorepo-release-pipelineInstalls into the current project.
Run `npx skills use "https://github.com/sirkirby/unifi-mcp" --skill "sirkirby/unifi-mcp/monorepo-release-pipeline"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/sirkirby/unifi-mcp" that are relevant to the current task. Run `npx skills add "https://github.com/sirkirby/unifi-mcp"` and select the relevant skills, then follow their instructions.