@staff0rd/assist 0.422.0 → 0.423.1

package/dist/index.js

@@ -6,7 +6,7 @@ import { Command } from "commander";
 // package.json
 var package_default = {
   name: "@staff0rd/assist",
-  version: "0.422.0",
+  version: "0.423.1",
   type: "module",
   main: "dist/index.js",
   bin: {
@@ -426,7 +426,8 @@ var assistConfigSchema = z2.strictObject({
   }).optional(),
   prs: z2.strictObject({
     slack: z2.string().optional(),
-    required: z2.boolean().default(false)
+    required: z2.boolean().default(false),
+    promptJira: z2.boolean().default(false)
   }).optional(),
   repos: z2.record(z2.string(), z2.record(z2.string(), z2.unknown())).optional(),
   run: z2.array(z2.union([runConfigSchema, runLinkSchema])).optional(),
@@ -1625,9 +1626,9 @@ function findUnmergedPaths() {
 }
 
 // src/commands/commit/abortOnConflicts.ts
-function abort(headline, guidance) {
+function abort(headline, guidance2) {
   console.error(`Error: refusing to commit \u2014 ${headline}`);
-  console.error(guidance);
+  console.error(guidance2);
   console.error("Nothing was committed or pushed.");
   process.exit(1);
 }
@@ -18487,6 +18488,11 @@ var prsConfigHelp = [
     key: "prs.required",
     setter: "assist config set prs.required true",
     note: "require a branch when running a backlog item"
+  },
+  {
+    key: "prs.promptJira",
+    setter: "assist config set prs.promptJira true",
+    note: "'assist prs raise' help asks the user for a Jira key to --resolves (default false)"
   }
 ];
 
@@ -18506,7 +18512,18 @@ function registerPrsEdit(prsCommand) {
 }
 
 // src/commands/prs/raiseHelpText.ts
-var GUIDANCE = `Raise a pull request for the current branch. Use a concise description with no
+var RESOLVES_WITH_PROMPT = `  --resolves <key>  Jira issue key resolved by this PR; repeatable. Each key's
+                    browse URL is appended inline to ## Why. Unless a Jira key is
+                    already known from the session, ask the user whether this PR
+                    resolves a Jira issue and for the key before raising; omit
+                    --resolves only if they say there isn't one.`;
+var RESOLVES_NO_PROMPT = `  --resolves <key>  Jira issue key resolved by this PR; repeatable. Each key's
+                    browse URL is appended inline to ## Why. Pass it when a Jira
+                    key is known from the session or supplied by the user; omit
+                    it otherwise.`;
+function guidance(promptJira) {
+  const resolves = promptJira ? RESOLVES_WITH_PROMPT : RESOLVES_NO_PROMPT;
+  return `Raise a pull request for the current branch. Use a concise description with no
 headers, and do not reference Claude or any AI assistance in the title or body.
 
 The body is assembled from discrete section options; supply at minimum --title,
@@ -18517,11 +18534,7 @@ The body is assembled from discrete section options; supply at minimum --title,
   --why <why>       why the change is needed (rendered as ## Why).
   --how <how>       optional; how the change works (rendered as ## How). Omit it
                     unless the approach genuinely needs explaining.
-  --resolves <key>  Jira issue key resolved by this PR; repeatable. Each key's
-                    browse URL is appended inline to ## Why. Unless a Jira key is
-                    already known from the session, ask the user whether this PR
-                    resolves a Jira issue and for the key before raising; omit
-                    --resolves only if they say there isn't one.
+${resolves}
 
 Wrap symbols, file paths, function names, class names, variable names, config
 keys, CLI commands, and flag names in backticks.
@@ -18562,6 +18575,7 @@ will be rejected.
 If a pull request already exists for the branch, this command errors \u2014 pass
 --force to fully overwrite its title and body, or use 'assist prs edit' to update
 only individual sections (every other section of the existing body is preserved).`;
+}
 var TERMINAL_CONFIRM = `Before running this command, the user must see the full proposed title and body \u2014
 do not assume they can see your reasoning or earlier tool output. Write the
 complete title and body verbatim in your visible reply, then use the
@@ -18579,10 +18593,11 @@ inline comments to specific spans of the preview; on rejection these are printed
 as numbered quoted-span + note pairs on stderr. Address every comment (and the
 reason), then run the command again to re-preview the revised PR. Repeat until it
 is approved. Just compose the sections and run the command.`;
-function raiseHelpText() {
+function raiseHelpText(promptJira) {
+  const prompt = promptJira ?? loadConfig().prs?.promptJira ?? false;
   const confirm = process.env.ASSIST_SESSION === "1" ? WEB_CONFIRM : TERMINAL_CONFIRM;
   return `
-${GUIDANCE}
+${guidance(prompt)}
 
 ${confirm}
 `;

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@staff0rd/assist",
-	"version": "0.422.0",
+	"version": "0.423.1",
 	"type": "module",
 	"main": "dist/index.js",
 	"bin": {