opencode-onboard 0.4.2 → 0.4.4

package/content/.agents/skills/ob-pullrequest-az/SKILL.md

@@ -1,160 +1,168 @@
----
-name: ob-pullrequest-az
-description: Create Azure DevOps PRs with screenshots, or read and triage PR review feedback. Use when shipping a feature branch or when user says "I've added comments to the PR".
-license: MIT
-compatibility: Requires az CLI, az devops extension, openspec CLI, and opencode-browser for screenshots.
-metadata:
-  author: copilots
-  version: "1.0"
----
-
-**Browser MCP tools are FORBIDDEN for all Azure DevOps operations.**
-Browser tools are ONLY permitted for screenshots of the LOCAL running app on `localhost` URLs.
-
----
-
-## Mode A: Create PR (ship mode)
-
-Triggered when devops-manager is in ship mode after implementation is complete.
-
-### Step 1: Verify feature branch
-
-```bash
-git branch --show-current
-```
-
-Branch must be `feature/{id}-{slug}`. NEVER push to `main`.
-
-### Step 2: Capture screenshots (if UI changes exist)
-
-```bash
-browser_navigate url="http://localhost:{port}/{route}"
-browser_wait ms=2000
-browser_screenshot
-```
-
-Save to: `openspec/changes/{change-name}/images/{feature}.png`
-
-### Step 3: Commit and push
-
-```bash
-git add .
-git commit -m "feat(#{id}): {description}"
-git push origin feature/{id}-{slug}
-```
-
-### Step 4: Create PR
-
-```bash
-az repos pr create \
-  --repository {repo} \
-  --source-branch feature/{id}-{slug} \
-  --target-branch main \
-  --title "feat(#{id}): {title}" \
-  --description "{description}"
-```
-
-### Step 5: Link work item (MANDATORY, run sequentially, not in parallel)
-
-```bash
-az repos pr work-item add --id {pr-id} --work-items {workitem-id}
-```
-
-### Step 6: Post screenshot comment
-
-Build raw URL for each image:
-```
-https://dev.azure.com/{org}/{project}/_apis/git/repositories/{repo}/items?path=openspec/changes/{change}/images/{file}.png&versionType=branch&version={branch}&api-version=7.1
-```
-
-Post via:
-```bash
-az devops invoke \
-  --area git --resource pullRequestThreads \
-  --route-parameters project={project} repositoryId={repo} pullRequestId={pr-id} \
-  --http-method POST --api-version 7.1 --in-file body.json
-```
-
-`body.json`:
-```json
-{
-  "comments": [{
-    "parentCommentId": 0,
-    "content": "## Screenshots\n\n![{feature}]({raw-url})",
-    "commentType": 1
-  }],
-  "status": "active"
-}
-```
-
----
-
-## Mode B: Read PR Feedback (feedback mode)
-
-Triggered when user says "I've added comments to the PR" or "check PR feedback".
-
-### Step 1: Find PRs
-
-If PR link provided, extract ID from URL. Otherwise:
-```bash
-az repos pr list --repository {repo} --status active --top 1
-```
-
-### Step 2: Read comment threads
-
-```bash
-az devops invoke \
-  --area git --resource pullRequestThreads \
-  --route-parameters project={project} repositoryId={repo} pullRequestId={id} \
-  --http-method GET --api-version 7.1
-```
-
-### Step 3: Categorize feedback
-
-| Category | Description | Action |
-|----------|-------------|--------|
-| `code-change` | Reviewer requests code modification | Return to lead to spawn specialists |
-| `spec-update` | Affects proposal, design, or tasks | Update openspec artifacts |
-| `question` | Reviewer asks a question | Reply with answer |
-| `resolved` | Thread already resolved | Skip |
-
-### Step 4: Update openspec (if spec-update)
-
-```bash
-git branch --show-current
-# feature/193208-roles-crud → change: us-193208-roles-crud
-```
-
-Update: `openspec/changes/{change}/proposal.md`, `design.md`, or `tasks.md` as appropriate.
-
-### Step 5: Reply to each thread
-
-```bash
-az devops invoke \
-  --area git --resource pullRequestThreadComments \
-  --route-parameters project={project} repositoryId={repo} pullRequestId={id} threadId={tid} \
-  --http-method POST --api-version 7.1 --in-file reply.json
-```
-
-`reply.json`:
-```json
-{
-  "comments": [{
-    "parentCommentId": 1,
-    "content": "Acknowledged, applying this change now.",
-    "commentType": 1
-  }]
-}
-```
-
----
-
-## Guardrails
-
-- ✅ Commit and push to feature branches only
-- ✅ Create and comment on PRs via az CLI
-- ✅ Screenshots of localhost only via browser_screenshot
-- ❌ Commit or push to `main`, FORBIDDEN
-- ❌ Force push, FORBIDDEN
-- ❌ Merge or approve PRs, human-only
-- ❌ Navigate browser to dev.azure.com, FORBIDDEN
+---
+name: ob-pullrequest-az
+description: Create Azure DevOps PRs with screenshots, or read and triage PR review feedback. Use when shipping a feature branch or when user says "I've added comments to the PR".
+license: MIT
+compatibility: Requires az CLI, az devops extension, openspec CLI, and opencode-browser for screenshots.
+metadata:
+  author: copilots
+  version: "1.0"
+---
+
+**Browser MCP tools are FORBIDDEN for all Azure DevOps operations.**
+Browser tools are ONLY permitted for screenshots of the LOCAL running app on `localhost` URLs.
+
+---
+
+## Mode A: Create PR (ship mode)
+
+Triggered when devops-manager is in ship mode after implementation is complete.
+
+### Step 1: Verify feature branch
+
+```bash
+git branch --show-current
+```
+
+Branch must be `feature/{id}-{slug}`. NEVER push to `main`.
+
+### Step 2: Capture screenshots (if UI changes exist)
+
+```bash
+browser_navigate url="http://localhost:{port}/{route}"
+browser_wait ms=2000
+browser_screenshot
+```
+
+Save to: `openspec/changes/{change-name}/images/{feature}.png`
+
+### Step 3: Commit and push
+
+```bash
+git add .
+git commit -m "feat(#{id}): {description}"
+git push origin feature/{id}-{slug}
+```
+
+### Step 4: Create PR
+
+```bash
+az repos pr create \
+  --repository {repo} \
+  --source-branch feature/{id}-{slug} \
+  --target-branch main \
+  --title "feat(#{id}): {title}" \
+  --description "{description}"
+```
+
+### Step 5: Link work item (MANDATORY, run sequentially, not in parallel)
+
+```bash
+az repos pr work-item add --id {pr-id} --work-items {workitem-id}
+```
+
+### Step 6: Post screenshot comment
+
+Build raw URL for each image:
+
+```
+https://dev.azure.com/{org}/{project}/_apis/git/repositories/{repo}/items?path=openspec/changes/{change}/images/{file}.png&versionType=branch&version={branch}&api-version=7.1
+```
+
+Post via:
+
+```bash
+az devops invoke \
+  --area git --resource pullRequestThreads \
+  --route-parameters project={project} repositoryId={repo} pullRequestId={pr-id} \
+  --http-method POST --api-version 7.1 --in-file body.json
+```
+
+`body.json`:
+
+```json
+{
+  "comments": [
+    {
+      "parentCommentId": 0,
+      "content": "## Screenshots\n\n![{feature}]({raw-url})",
+      "commentType": 1
+    }
+  ],
+  "status": "active"
+}
+```
+
+---
+
+## Mode B: Read PR Feedback (feedback mode)
+
+Triggered when user says "I've added comments to the PR" or "check PR feedback".
+
+### Step 1: Find PRs
+
+If PR link provided, extract ID from URL. Otherwise:
+
+```bash
+az repos pr list --repository {repo} --status active --top 1
+```
+
+### Step 2: Read comment threads
+
+```bash
+az devops invoke \
+  --area git --resource pullRequestThreads \
+  --route-parameters project={project} repositoryId={repo} pullRequestId={id} \
+  --http-method GET --api-version 7.1
+```
+
+### Step 3: Categorize feedback
+
+| Category      | Description                         | Action                              |
+| ------------- | ----------------------------------- | ----------------------------------- |
+| `code-change` | Reviewer requests code modification | Return to lead to spawn specialists |
+| `spec-update` | Affects proposal, design, or tasks  | Update openspec artifacts           |
+| `question`    | Reviewer asks a question            | Reply with answer                   |
+| `resolved`    | Thread already resolved             | Skip                                |
+
+### Step 4: Update openspec (if spec-update)
+
+```bash
+git branch --show-current
+# feature/193208-roles-crud → change: us-193208-roles-crud
+```
+
+Update: `openspec/changes/{change}/proposal.md`, `design.md`, or `tasks.md` as appropriate.
+
+### Step 5: Reply to each thread
+
+```bash
+az devops invoke \
+  --area git --resource pullRequestThreadComments \
+  --route-parameters project={project} repositoryId={repo} pullRequestId={id} threadId={tid} \
+  --http-method POST --api-version 7.1 --in-file reply.json
+```
+
+`reply.json`:
+
+```json
+{
+  "comments": [
+    {
+      "parentCommentId": 1,
+      "content": "Acknowledged, applying this change now.",
+      "commentType": 1
+    }
+  ]
+}
+```
+---
+
+## Guardrails
+
+- ✅ Commit and push to feature branches only
+- ✅ Create and comment on PRs via az CLI
+- ✅ Screenshots of localhost only via browser_screenshot
+- ❌ Commit or push to `main`, FORBIDDEN
+- ❌ Force push, FORBIDDEN
+- ❌ Merge or approve PRs, human-only
+- ❌ Navigate browser to dev.azure.com, FORBIDDEN

package/content/.agents/skills/ob-pullrequest-gh/SKILL.md

@@ -1,136 +1,140 @@
----
-name: ob-pullrequest-gh
-description: Create GitHub PRs with screenshots, or read and triage PR review feedback. Use when shipping a feature branch or when user says "I've added comments to the PR".
-license: MIT
-compatibility: Requires gh CLI, openspec CLI, and opencode-browser for screenshots.
-metadata:
-  author: copilots
-  version: "1.0"
----
-
-**ALL GitHub data MUST come from `gh` CLI. NEVER use webfetch, HTTP requests, or browser MCP tools for GitHub operations, even if gh CLI fails. If `gh` is unavailable, report as a blocker.**
-Always pass `--repo {owner}/{repo}` explicitly, never rely on git context to resolve the repo.
-
----
-
-## Mode A: Create PR (ship mode)
-
-Triggered when devops-manager is in ship mode after implementation is complete.
-
-### Step 1: Verify feature branch
-
-```bash
-git branch --show-current
-```
-
-Branch must be `feature/{id}-{slug}`. NEVER push to `main`.
-
-### Step 2: Capture screenshots (if UI changes exist)
-
-```bash
-browser_navigate url="http://localhost:{port}/{route}"
-browser_wait ms=2000
-browser_screenshot
-```
-
-Save to: `openspec/changes/{change-name}/images/{feature}.png`
-
-### Step 3: Commit and push
-
-```bash
-git add .
-git commit -m "feat(#{id}): {description}"
-git push origin feature/{slug}
-```
-
-### Step 4: Create PR
-
-```bash
-gh pr create \
-  --base main \
-  --head feature/{slug} \
-  --title "feat: {title}" \
-  --body "{description}"
-```
-
-### Step 5: Post screenshot comment
-
-Resolve commit SHA (the commit that includes screenshots):
-```bash
-git rev-parse HEAD
-```
-
-Build blob URL for each image (preferred, stable in PR discussion):
-```
-https://github.com/{owner}/{repo}/blob/{sha}/openspec/changes/{change}/images/{file}.png
-```
-
-Post comment:
-```bash
-gh pr comment {pr-number} --repo {owner}/{repo} --body $'## Screenshots\n\n![{feature}]({blob-url})'
-```
-
----
-
-## Mode B: Read PR Feedback (feedback mode)
-
-Triggered when user says "I've added comments to the PR" or "check PR feedback".
-
-### Step 1: Find PRs
-
-If PR link provided, extract number from URL. Otherwise:
-```bash
-gh pr list --repo {owner}/{repo} --state open --limit 1
-```
-
-### Step 2: Read comment threads
-
-```bash
-gh pr view {pr-number} --repo {owner}/{repo} --comments
-# Or structured output:
-gh api repos/{owner}/{repo}/pulls/{pr-number}/comments
-gh api repos/{owner}/{repo}/pulls/{pr-number}/reviews
-```
-
-### Step 3: Categorize feedback
-
-| Category | Description | Action |
-|----------|-------------|--------|
-| `code-change` | Reviewer requests code modification | Return to lead to spawn specialists |
-| `spec-update` | Affects proposal, design, or tasks | Update openspec artifacts |
-| `question` | Reviewer asks a question | Reply with answer |
-| `resolved` | Thread already resolved | Skip |
-
-### Step 4: Update openspec (if spec-update)
-
-```bash
-git branch --show-current
-# feature/add-user-auth → change: add-user-auth
-```
-
-Update: `openspec/changes/{change}/proposal.md`, `design.md`, or `tasks.md` as appropriate.
-
-### Step 5: Reply to each comment thread
-
-```bash
-# Reply to a review comment
-gh api repos/{owner}/{repo}/pulls/{pr-number}/comments/{comment-id}/replies \
-  --method POST \
-  --field body="Acknowledged, applying this change now."
-
-# Or post a general PR comment
-gh pr comment {pr-number} --body "Updated design.md to reflect feedback."
-```
-
----
-
-## Guardrails
-
-- ✅ Commit and push to feature branches only
-- ✅ Create and comment on PRs via gh CLI with explicit `--repo {owner}/{repo}`
-- ✅ Screenshots of localhost only via browser_screenshot
-- ❌ Commit or push to `main`, FORBIDDEN
-- ❌ Force push, FORBIDDEN
-- ❌ Merge or approve PRs, human-only
-- ❌ Navigate browser to github.com, FORBIDDEN
-- ❌ webfetch or HTTP requests to GitHub URLs, FORBIDDEN
+---
+name: ob-pullrequest-gh
+description: Create GitHub PRs with screenshots, or read and triage PR review feedback. Use when shipping a feature branch or when user says "I've added comments to the PR".
+license: MIT
+compatibility: Requires gh CLI, openspec CLI, and opencode-browser for screenshots.
+metadata:
+  author: copilots
+  version: "1.0"
+---
+
+**ALL GitHub data MUST come from `gh` CLI. NEVER use webfetch, HTTP requests, or browser MCP tools for GitHub operations, even if gh CLI fails. If `gh` is unavailable, report as a blocker.**
+Always pass `--repo {owner}/{repo}` explicitly, never rely on git context to resolve the repo.
+
+---
+
+## Mode A: Create PR (ship mode)
+
+Triggered when devops-manager is in ship mode after implementation is complete.
+
+### Step 1: Verify feature branch
+
+```bash
+git branch --show-current
+```
+
+Branch must be `feature/{id}-{slug}`. NEVER push to `main`.
+
+### Step 2: Capture screenshots (if UI changes exist)
+
+```bash
+browser_navigate url="http://localhost:{port}/{route}"
+browser_wait ms=2000
+browser_screenshot
+```
+
+Save to: `openspec/changes/{change-name}/images/{feature}.png`
+
+### Step 3: Commit and push
+
+```bash
+git add .
+git commit -m "feat(#{id}): {description}"
+git push origin feature/{id}-{slug}
+```
+
+### Step 4: Create PR
+
+```bash
+gh pr create \
+  --base main \
+  --head feature/{id}-{slug} \
+  --title "feat(#{id}): {title}" \
+  --body "{description}"
+```
+
+### Step 5: Post screenshot comment
+
+Resolve commit SHA (the commit that includes screenshots):
+
+```bash
+git rev-parse HEAD
+```
+
+Build blob URL for each image (preferred, stable in PR discussion):
+
+```
+https://github.com/{owner}/{repo}/blob/{sha}/openspec/changes/{change}/images/{file}.png
+```
+
+Post comment:
+
+```bash
+gh pr comment {pr-number} --repo {owner}/{repo} --body $'## Screenshots\n\n![{feature}]({blob-url})'
+```
+
+---
+
+## Mode B: Read PR Feedback (feedback mode)
+
+Triggered when user says "I've added comments to the PR" or "check PR feedback".
+
+### Step 1: Find PRs
+
+If PR link provided, extract number from URL. Otherwise:
+
+```bash
+gh pr list --repo {owner}/{repo} --state open --limit 1
+```
+
+### Step 2: Read comment threads
+
+```bash
+gh pr view {pr-number} --repo {owner}/{repo} --comments
+# Or structured output:
+gh api repos/{owner}/{repo}/pulls/{pr-number}/comments
+gh api repos/{owner}/{repo}/pulls/{pr-number}/reviews
+```
+
+### Step 3: Categorize feedback
+
+| Category      | Description                         | Action                              |
+| ------------- | ----------------------------------- | ----------------------------------- |
+| `code-change` | Reviewer requests code modification | Return to lead to spawn specialists |
+| `spec-update` | Affects proposal, design, or tasks  | Update openspec artifacts           |
+| `question`    | Reviewer asks a question            | Reply with answer                   |
+| `resolved`    | Thread already resolved             | Skip                                |
+
+### Step 4: Update openspec (if spec-update)
+
+```bash
+git branch --show-current
+# feature/add-user-auth → change: add-user-auth
+```
+
+Update: `openspec/changes/{change}/proposal.md`, `design.md`, or `tasks.md` as appropriate.
+
+### Step 5: Reply to each comment thread
+
+```bash
+# Reply to a review comment
+gh api repos/{owner}/{repo}/pulls/{pr-number}/comments/{comment-id}/replies \
+  --method POST \
+  --field body="Acknowledged, applying this change now."
+
+# Or post a general PR comment
+gh pr comment {pr-number} --body "Updated design.md to reflect feedback."
+```
+
+---
+
+## Guardrails
+
+- ✅ Commit and push to feature branches only
+- ✅ Create and comment on PRs via gh CLI with explicit `--repo {owner}/{repo}`
+- ✅ Screenshots of localhost only via browser_screenshot
+- ❌ Commit or push to `main`, FORBIDDEN
+- ❌ Force push, FORBIDDEN
+- ❌ Merge or approve PRs, human-only
+- ❌ Navigate browser to github.com, FORBIDDEN
+- ❌ webfetch or HTTP requests to GitHub URLs, FORBIDDEN