@devflow-one/cli 0.1.14 → 0.1.16

package/README.md

@@ -182,6 +182,8 @@ devflow mr create "Title" feat/x --base release/2026.4 --project ABC
 # stamped with. Omitted or unrecognized, it is auto-selected by matching configured
 # type names against the title's conventional prefix, branch prefix, Jira issue type
 # and title keywords, falling back to the first type. Pass its id or label to pick one.
+# The template (its own {prMedia} uploads media) writes the description; --body is the
+# fallback, where {prMedia} is filled or removed.
 devflow mr create "Title" feat/x --type Bugfix --project ABC
 devflow mr types --project ABC                # configured types: id, label, default flag
 
@@ -204,17 +206,42 @@ devflow commit template /wt/ABC-123 --no-push --project ABC   # commit locally,
 
 # read a PR/MR's title + description, then edit it: --title/--description replace,
 # --append-description adds text after a `---` rule (skipped if already at the end);
-# --base retargets the PR/MR to an existing remote branch
+# --base retargets the PR/MR to an existing remote branch; `{prMedia}` in the description
+# uploads .devflow/media/<ISSUE-KEY>[-n].{mp4,png,jpg,jpeg} and is replaced with the links
+# (removed when the upload fails or the head branch names no issue; media.error says why)
 devflow mr get 42 --project ABC
 devflow mr update 42 --append-description "## Test plan" --project ABC
 devflow mr update 42 --title "Fix login redirect" --project ABC
 devflow mr update 42 --base release/2026.4 --project ABC
+devflow mr update 42 --description "$(cat body.md)" --project ABC   # body.md has {prMedia}
 
 # assembled fix-review-comments prompt (read-only; runs no AI, makes no writes)
 devflow mr fix-prompt 42                    # issue key inferred from the branch
 
+# issue status and the repo card's branches and PRs/MRs (read-only; the issue key is
+# inferred from the branch). Status needs the Jira API token set in Settings.
+devflow issue status                        # the issue's and its parent's status
+devflow issue branches ABC-123 --project ABC
+devflow issue prs                           # every state, merged and closed included
+
+# review comments: counts, then "Reply as Fixed" or an AI "Fix Comments" run, which
+# commits and pushes (so it needs --force). It returns at once: `started`, `prNumber` and
+# `queued` (true when an automation run is busy, so the fix starts on its next tick), or
+# `started: false` with a `reason` — e.g. while the panel or the timer is fixing that PR
+devflow mr comments 42                      # unfixed / fixed / resolved / prComments
+devflow mr reply-fixed 42                   # success / failed / resolved counts
+devflow mr fix-comments 42 --force           # then re-check the counts
+
 # notify the project's configured Slack channel(s)
 devflow slack notify "Review fixes ready on {pr}" --values '{"pr":"#42"}' --project ABC
+devflow slack channels --project ABC         # configured channels (read-only, no credentials)
+
+# reviewer notify: per channel, were reviewers already notified, and is the next step a
+# send or a ping? `source` says who posted: manual (panel), auto (auto-send), gateway
+# (`slack notify --pr`) or slack (found only in Slack history). `--pr` records the post
+# and threads a ping under the earlier message
+devflow mr notify-status 42
+devflow slack notify "Please review #42" --channel C123 --pr 42
 
 # force a specific profile when a key is ambiguous
 devflow mr ready 12 --profile prof-1
@@ -222,7 +249,8 @@ devflow mr ready 12 --profile prof-1
 
 ### Destructive actions
 
-`branch delete`, `mr close` and `mr merge` are destructive. They are **refused
+`branch delete`, `mr close`, `mr merge`, `mr fix-comments` (its AI run commits and
+pushes) and `commit template` (unless `--no-push`) are destructive. They are **refused
 unless you confirm** with `--force` (or `--yes`); the gateway enforces the same
 gate server-side, so the confirmation can't be bypassed:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devflow-one/cli",
-  "version": "0.1.14",
+  "version": "0.1.16",
   "description": "Terminal CLI wrapping the local DevFlow gateway so shell scripts can trigger repo actions.",
   "keywords": [
     "devflow",

package/src/commands.js

@@ -218,6 +218,32 @@ const COMMANDS = {
     },
   },
 
+  "issue status": {
+    method: "POST",
+    action: "getIssueStatus",
+    usage:
+      "issue status [issueKey] [--issue KEY] [--project KEY]" +
+      " (the issue's and its parent's Jira status; needs the Jira API token source; read-only)",
+    buildArgs: issueKeyArgs("issue status"),
+  },
+  "issue branches": {
+    method: "POST",
+    action: "listIssueBranches",
+    usage:
+      "issue branches [issueKey] [--issue KEY] [--project KEY]" +
+      " (each repo's remote branches for the issue and its parent, as the repo card lists them; read-only)",
+    buildArgs: issueKeyArgs("issue branches"),
+  },
+  "issue prs": {
+    method: "POST",
+    action: "listIssuePullRequests",
+    usage:
+      "issue prs [issueKey] [--issue KEY] [--project KEY]" +
+      " (each repo's PRs/MRs for the issue in every state, merged and closed included, with" +
+      " approvers on open ones; read-only)",
+    buildArgs: issueKeyArgs("issue prs"),
+  },
+
   "mr create": {
     method: "POST",
     retryUnsafe: true,
@@ -228,7 +254,8 @@ const COMMANDS = {
       " (a headBranch that exists on the remote is used as is; otherwise the repo's branch" +
       " template picks the head branch from the issue; --base defaults to the repo's configured base branch, expanding a {year}/{number} pattern;" +
       " --type is auto-selected by matching PR type names against the title prefix, branch prefix," +
-      " Jira issue type and title keywords, falling back to the first configured type)",
+      " Jira issue type and title keywords, falling back to the first configured type;" +
+      " the description comes from the PR type template, --body is the fallback where {prMedia} is filled or removed)",
     buildArgs: ([title, headBranch], flags, context = {}) => {
       const issueKey = templateIssueKey(headBranch, flags, context);
 
@@ -341,7 +368,10 @@ const COMMANDS = {
       " [--base <branch>] [--issue KEY] [--project KEY]" +
       " (--title/--description replace; --append-description adds text after a `---` rule" +
       " and is skipped if it already ends the description after that rule; --base retargets" +
-      " the PR/MR to an existing remote branch)",
+      " the PR/MR to an existing remote branch; `{prMedia}` in --description or" +
+      " --append-description uploads .devflow/media/<ISSUE-KEY>[-n].{mp4,png,jpg,jpeg} and is" +
+      " replaced with the links, so swap old media links for `{prMedia}` to refresh them." +
+      " It is removed if the upload fails or the head branch names no issue; media.error says why)",
     buildArgs: ([prId], flags) => {
       const title = toText("title", flags.title);
       const body = toRawText("description", flags.description);
@@ -377,6 +407,46 @@ const COMMANDS = {
       return [parsedPrId, context.issueKey];
     },
   },
+  "mr comments": {
+    method: "POST",
+    action: "getPrReviewCommentCounts",
+    usage:
+      "mr comments <prId> [--issue KEY] [--project KEY]" +
+      " (unfixed / fixed / resolved review-thread and PR-level comment counts; read-only)",
+    buildArgs: ([prId]) => [toInt("prId", prId)],
+  },
+  "mr notify-status": {
+    method: "POST",
+    action: "getReviewerNotifyStatus",
+    usage:
+      "mr notify-status <prId> [--issue KEY] [--project KEY]" +
+      " (per reviewer channel: whether reviewers were already notified on Slack and whether the" +
+      " next step is a send or a ping, and who posted; follow up with `slack notify` for that" +
+      " PR; read-only)",
+    buildArgs: ([prId]) => [toInt("prId", prId)],
+  },
+  "mr fix-comments": {
+    method: "POST",
+    retryUnsafe: true,
+    action: "fixPrComments",
+    destructive: true,
+    usage:
+      "mr fix-comments <prId> [--issue KEY] [--project KEY] --force" +
+      " (starts an AI fix of the PR's unresolved review comments, which commits and pushes;" +
+      " returns at once: started / prNumber / queued, or a reason it was refused, e.g. that PR" +
+      " is already being fixed; re-check with `mr comments`)",
+    buildArgs: ([prId]) => [toInt("prId", prId)],
+  },
+  "mr reply-fixed": {
+    method: "POST",
+    retryUnsafe: true,
+    action: "replyPrCommentsFixed",
+    usage:
+      "mr reply-fixed <prId> [--issue KEY] [--project KEY]" +
+      ' (replies "Fixed" to every unanswered review thread, resolving it when the repo is set to;' +
+      " prints success / failed counts)",
+    buildArgs: ([prId]) => [toInt("prId", prId)],
+  },
   "pipeline status": {
     method: "POST",
     action: "getPipelineStatus",
@@ -423,16 +493,27 @@ const COMMANDS = {
     retryUnsafe: true,
     action: "notifySlack",
     usage:
-      'slack notify <message> [--channel ID] [--values \'{"key":"val"}\'] [--issue KEY] [--project KEY]',
+      'slack notify <message> [--channel ID] [--values \'{"key":"val"}\'] [--pr <prId>]' +
+      " [--issue KEY] [--project KEY]" +
+      " (--pr records the post as that PR's reviewer notify; a channel already notified for it" +
+      " gets a ping threaded under the earlier message)",
     buildArgs: ([message], flags) => {
       if (!message) throw new UsageError("slack notify requires <message>.");
 
       const channel = flags.channel ? String(flags.channel) : undefined;
       const values = toValues("values", flags.values);
 
-      return [message, channel, values];
+      if (flags.pr === undefined) return [message, channel, values];
+
+      return [message, channel, values, { prNumber: toInt("pr", String(flags.pr)) }];
     },
   },
+  "slack channels": {
+    method: "POST",
+    action: "listSlackChannels",
+    usage: "slack channels [--issue KEY] [--project KEY] (configured channels; read-only)",
+    buildArgs: () => [],
+  },
 };
 
 /**