@brunyee-studio/onus-cli 2.29.0 → 2.30.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@brunyee-studio/onus-cli",
-  "version": "2.29.0",
+  "version": "2.30.0",
   "description": "Official CLI and TypeScript SDK for Onus issue tracking platform",
   "keywords": [
     "agent",

package/skills/onus-cli/SKILL.md

@@ -145,24 +145,34 @@ onus dsn create --team ONUS --label ci    # prints the full secret exactly once
 ## Pull requests and issues
 
 Linking a PR to an issue means **the issue is auto-closed when the PR merges** —
-there is no "related" link type. How links are created:
-
-- **Auto-linking is GitHub-style.** The integration scans the PR title, body,
-  and branch name for `KEY-123` refs introduced by a closing keyword —
-  `Fixes` / `Closes` / `Resolves` (case-insensitive, optional colon, comma/
-  `and` lists). A plain prose mention of an issue ID does NOT link and never
-  auto-closes, so avoid writing bare issue IDs in PR text: use the issue's
-  name or its Onus URL instead.
-- **Manual linking is deliberate.** `onus issue link-pr` creates a bot link
-  that survives body edits and closes on merge — use it when the PR fully
-  resolves an issue but its text has no closing keyword.
-- **Only link PRs that actually fix/close the issue.** If a PR merely touches
-  related code, discusses the issue, or implements part of it without completing
-  it, do NOT link it (no keyword in the PR text, no `link-pr`). Use a relation
-  (`onus issue relation add … --type related`) or a comment mention instead.
-- Never guess or assume: before linking, verify the PR's changes fully resolve
-  the issue (e.g. you implemented the fix in that PR, or the PR description
-  says "Fixes ONUS-42").
+there is no "related" link type.
+
+**Always link manually with `onus issue link-pr`. Never rely on the fix
+keyword.** The integration also scans the PR title, body, and branch name for
+`KEY-123` refs introduced by a closing keyword (`Fixes` / `Closes` /
+`Resolves` — case-insensitive, optional colon, comma/`and` lists), but agents
+must never depend on that scan and must never write a closing keyword before
+an Onus issue ref in PR text or a branch name. Reference issues in PR text by
+name or their Onus URL, never as bare issue IDs.
+
+Required PR flow, in order:
+
+1. **Create the PR** (push the branch, open the PR with `gh`).
+2. **Determine whether the PR closes the issue.** It closes the issue only if
+   the PR fully resolves it — you implemented the whole fix in that PR. A PR
+   that merely touches related code, discusses the issue, or implements part
+   of it without completing it does not close it.
+3. **Link it.** If (and only if) step 2 says yes, run:
+
+   ```bash
+   onus issue link-pr <ref> --repo owner/repo --pr <number> --json
+   ```
+
+   The bot link survives PR-body edits and closes the issue on merge. If the
+   PR does not close the issue, leave it unlinked — use a relation
+   (`onus issue relation add … --type related`) or a comment mention instead.
+
+- Never guess or assume: link only issues you know the PR fully resolves.
 - Link at most once per PR per issue; don't spam links across partially-related
   issues.