release

# Release Publish packages to their registries. Works with single packages and monorepos. ## Arguments `$ARGUMENTS` may contain: - A version number: `1.2.3`, `1.2.3-alpha.1`, `patch`, `minor`, `major` - A package path for monorepos: `rush/app`, `harness-ui` - Flags: `--skip-tests`, `--skip-build`, `--force` If no version is given, analyze what's needed and suggest one. --- ## Phase 1: Discovery Before doing anything, check for project-specific release instructions. ### 1.1 Check for project-level overrides ```bash # Project-level release skill takes precedence ls .agents/skills/release/ 2>/dev/null # Check for release instructions in project docs grep -l -i "release\|publish\|deploy" README.md CLAUDE.md AGENTS.md .agents/*.md 2>/dev/null | head -5 ``` If `.agents/skills/release/` exists in the project, defer to it completely. Read those instructions and follow them instead of this skill. ### 1.2 Detect repo structure ```bash # Is this a monorepo? if [[ -f "package.json" ]]; then # Check for workspaces jq -e '.workspaces' package.json 2>/dev/null && echo "MONOREPO: npm/bun workspaces" fi [[ -f "pnpm-workspace.yaml" ]] && echo "MONOREPO: pnpm workspaces" [[ -f "lerna.json" ]] && echo "MONOREPO: lerna" # Find all package.json files fd -t f package.json --max-depth 3 | head -20 ``` ### 1.3 Identify publishable packages ```bash # List packages that are NOT private fd -t f package.json --max-depth 3 -x sh -c ' name=$(jq -r ".name // empty" "{}") private=$(j...