@orderful/droid 0.42.1 → 0.44.0

package/src/tools/release/skills/release/references/templates.md

@@ -0,0 +1,104 @@
+# Release Templates
+
+Slack mrkdwn and PR body templates for release notifications.
+
+## Slack Messages
+
+All Slack messages are posted via `droid integrations slack post`. Format as Slack mrkdwn (not GitHub markdown).
+
+### Release Started
+
+```
+:rocket: *Release started — {repo_name}*
+
+*Risk:* {risk_emoji} {risk_level}
+*PR:* <{pr_url}|#{pr_number}>
+*Branch:* `{release_branch}` → `{production_branch}`
+
+{pr_summary}
+
+Posted with :droid:
+```
+
+Risk emojis:
+- Low Risk: `:large_green_circle:`
+- High Risk: `:warning:`
+
+### Release Merged
+
+```
+:merged-pr: *Release merged — {repo_name}*
+
+*PR:* <{pr_url}|#{pr_number}>
+*Branch:* `{release_branch}` → `{production_branch}`
+
+Monitoring deployment :eyes:
+
+Posted with :droid:
+```
+
+### Release Complete
+
+```
+:white_check_mark: *Release complete — {repo_name}*
+
+*PR:* <{pr_url}|#{pr_number}>
+*Branch:* `{release_branch}` → `{production_branch}`
+
+Posted with :droid:
+```
+
+---
+
+## Release PR Body
+
+Used when creating the release PR via `gh pr create --body`.
+
+```markdown
+### {repo_name} Release
+
+**Risk:** [{risk_level}]
+
+**When:** Imminent
+
+**PRs included:**
+{pr_list}
+
+---
+
+Created with :robot: [droid](https://github.com/Orderful/droid)
+```
+
+Where `{pr_list}` is a bulleted list of merged PRs:
+```markdown
+- #{number} {title} (@{author})
+- #{number} {title} (@{author})
+```
+
+---
+
+## Terminal Fallback
+
+When Slack is not configured, print a plain-text version to terminal:
+
+### Release Started (terminal)
+```
+Release started — {repo_name}
+  Risk: {risk_level}
+  PR:   {pr_url}
+  Branch: {release_branch} -> {production_branch}
+```
+
+### Release Merged (terminal)
+```
+Release merged — {repo_name}
+  PR:     {pr_url}
+  Branch: {release_branch} -> {production_branch}
+  Monitoring deployment...
+```
+
+### Release Complete (terminal)
+```
+Release complete — {repo_name}
+  PR: {pr_url}
+```

package/src/tools/release/skills/release/references/workflows.md

@@ -0,0 +1,166 @@
+# Release Workflows
+
+Detailed step-by-step procedures for each `/release` subcommand. All commands use `gh` CLI directly.
+
+## Common Setup (every command)
+
+```bash
+# 1. Read config
+SLACK_CHANNEL=$(droid config --get tools.release.slack_channel)
+# Default to #release-management if not set
+SLACK_CHANNEL="${SLACK_CHANNEL:-#release-management}"
+
+# 2. Get repos and filter for release repos (those with release_branch set)
+droid config --get repos
+# Parse JSON output — release repos have release_branch defined
+```
+
+Detect repo from cwd or ask user. Extract `release_branch`, `production_branch` (default: `master`), and the GitHub `owner/repo` slug from the repo's remote.
+
+```bash
+# Get owner/repo from git remote
+git -C {repo_path} remote get-url origin
+# Parse to extract owner/repo (e.g., "Orderful/orderful-workspace")
+```
+
+---
+
+## `/release start [repo]`
+
+Create a release PR and notify Slack.
+
+### Steps
+
+1. **Detect repo** — match cwd or ask user to pick from release repos
+
+2. **Check for existing release PR:**
+   ```bash
+   gh pr list --search "[RELEASE]" --state open --base {production_branch} --head {release_branch} --json number,title,url --repo {owner}/{repo}
+   ```
+   If one exists, show it and ask: "A release PR already exists. Open it instead?"
+
+3. **Generate release notes** — compare branches to find PRs included in this release:
+   ```bash
+   # Get commits in release_branch that aren't in production_branch
+   gh api repos/{owner}/{repo}/compare/{production_branch}...{release_branch} --jq '.commits[].commit.message'
+   ```
+   Extract PR numbers from commit messages (e.g. `(#1234)`) and format as a bulleted list for the PR body.
+
+   **Do NOT use** `gh pr list --base {release_branch} --state merged` — that returns ALL historically merged PRs, not just the ones since the last release.
+
+4. **Ask risk level** — use AskUserQuestion:
+   - Low Risk (routine release, no breaking changes)
+   - High Risk (breaking changes, data migrations, or high-traffic feature)
+
+5. **Create the release PR:**
+   ```bash
+   gh pr create \
+     --base {production_branch} \
+     --head {release_branch} \
+     --title "[RELEASE] {repo_name}" \
+     --label "READY" \
+     --body "{release_pr_body}" \
+     --repo {owner}/{repo}
+   ```
+   See `templates.md` for the PR body template.
+
+6. **Post to Slack:**
+   ```bash
+   node -e 'process.stdout.write(JSON.stringify({
+     channel: "{slack_channel}",
+     text: "{slack_message}",
+     unfurl_links: false
+   }))' | droid integrations slack post
+   ```
+   See `templates.md` for the Slack message template (release started).
+
+7. **Confirm to user** — show PR URL and Slack post confirmation.
+
+---
+
+## `/release merge [repo]`
+
+Merge the release PR if all checks are green, then notify Slack.
+
+### Steps
+
+1. **Detect repo** — match cwd or ask user
+
+2. **Find the open release PR:**
+   ```bash
+   gh pr list --search "[RELEASE]" --state open --base {production_branch} --head {release_branch} --json number,title,url,statusCheckRollup --repo {owner}/{repo}
+   ```
+   If no open release PR found, error: "No open release PR found. Run `/release start` first."
+
+3. **Check all status checks:**
+   Parse `statusCheckRollup` from the PR data. Every check must have `conclusion: "SUCCESS"` or `state: "SUCCESS"`.
+
+   If any checks are pending: "CI checks are still running on PR #{number}. Wait for them to finish."
+   If any checks are failing: "CI checks are failing on PR #{number}. Fix them before merging." Show the failing checks.
+
+4. **Confirm with user** — use AskUserQuestion:
+   "All checks are green on PR #{number}. Merge `{release_branch}` → `{production_branch}`?"
+
+5. **Merge the PR:**
+   ```bash
+   gh pr merge {pr_number} --merge --repo {owner}/{repo}
+   ```
+
+6. **Post to Slack** — release merged notification (see `templates.md`).
+
+7. **Confirm to user** — show merge confirmation and Slack post confirmation.
+
+---
+
+## `/release status`
+
+Check release status across all configured release repos.
+
+### Steps
+
+1. **Get all release repos** from config
+
+2. **For each release repo**, gather:
+
+   **Open release PRs:**
+   ```bash
+   gh pr list --search "[RELEASE]" --state open --json number,title,url,statusCheckRollup --repo {owner}/{repo}
+   ```
+
+3. **Format and display** as a summary:
+
+   ```
+   {repo_name}
+     Release PR: #{number} — {CI status} (green/pending/failing)
+   ```
+
+   If no open release PR: "No active release"
+   If no release repos configured: "No release repos configured"
+
+---
+
+## `/release complete [repo]`
+
+Close out a release — notify Slack.
+
+### Steps
+
+1. **Detect repo** — match cwd or ask user
+
+2. **Find the release PR:**
+   ```bash
+   # Check merged first
+   gh pr list --search "[RELEASE]" --state merged --base {production_branch} --head {release_branch} --json number,title,url,mergedAt --limit 1 --repo {owner}/{repo}
+   ```
+   If no merged PR found, check open:
+   ```bash
+   gh pr list --search "[RELEASE]" --state open --base {production_branch} --head {release_branch} --json number,title,url --repo {owner}/{repo}
+   ```
+   - If PR is still open (not merged): warn "Release PR #{number} is still open. Merge it first, or complete anyway?"
+   - If no PR found at all: warn "No release PR found. Post completion anyway?"
+
+3. **Post to Slack** — release complete notification (see `templates.md`).
+
+4. **Confirm to user:**
+   - "Release complete for `{repo_name}`"
+   - Show Slack message confirmation