@staff0rd/assist 0.361.0 → 0.362.1

package/dist/index.js

@@ -6,7 +6,7 @@ import { Command } from "commander";
 // package.json
 var package_default = {
   name: "@staff0rd/assist",
-  version: "0.361.0",
+  version: "0.362.1",
   type: "module",
   main: "dist/index.js",
   bin: {
@@ -6966,7 +6966,8 @@ import { execFile as execFile3 } from "child_process";
 import { promisify as promisify4 } from "util";
 var execFileAsync3 = promisify4(execFile3);
 var CACHE_TTL_MS = 3e4;
-function createCachedGhJson(args, parse3, fallback) {
+function createCachedGhJson(args, parse3, fallback, options2 = {}) {
+  const { cacheFallback = true } = options2;
   const cache = /* @__PURE__ */ new Map();
   return async (cwd, extraArgs = []) => {
     const key = extraArgs.length ? `${cwd}\0${extraArgs.join("\0")}` : cwd;
@@ -6983,7 +6984,8 @@ function createCachedGhJson(args, parse3, fallback) {
     } catch {
       value = fallback;
     }
-    cache.set(key, { value, expires: now + CACHE_TTL_MS });
+    if (cacheFallback || value !== fallback)
+      cache.set(key, { value, expires: now + CACHE_TTL_MS });
     return value;
   };
 }
@@ -7035,7 +7037,8 @@ var prFields = "number,title,author,createdAt,url";
 var getPrByNumber = createCachedGhJson(
   ["pr", "view", "--json", prFields],
   (stdout) => toPrSummary(JSON.parse(stdout)),
-  null
+  null,
+  { cacheFallback: false }
 );
 var getOpenPrForBranch = createCachedGhJson(
   ["pr", "list", "--state", "open", "--json", prFields],
@@ -7044,7 +7047,8 @@ var getOpenPrForBranch = createCachedGhJson(
     if (!Array.isArray(parsed) || parsed.length === 0) return null;
     return toPrSummary(parsed[0]);
   },
-  null
+  null,
+  { cacheFallback: false }
 );
 async function getCurrentBranch(cwd) {
   try {

package/package.json

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

package/claude/commands/associate-jira.md

@@ -1,34 +0,0 @@
----
-description: Associate a Jira ticket with a backlog item
-allowed_args: "<JIRA-KEY> [backlog item id]"
----
-
-You are associating a Jira ticket with a backlog item by calling the `assist backlog associate-jira` CLI command, which validates the key, confirms the issue exists in Jira, and stores it on the item.
-
-## Step 1: Parse arguments
-
-`$ARGUMENTS` contains a Jira key (e.g. `PROJ-123`) and an optional backlog item id. Identify which token is the Jira key (matches `[A-Z]+-\d+`) and which, if any, is the item id (a bare number).
-
-## Step 2: Resolve the target item
-
-If an explicit item id was provided, use it.
-
-Otherwise, use the backlog item this session is working on — the one you are implementing, reviewing, or otherwise focused on (e.g. via `/next-backlog-item`, a `backlog run`, or earlier in this conversation). Use its id directly.
-
-If there is no explicit id and this session is not working on a backlog item, there is nothing to associate the key with — tell the user and ask them to pass an explicit item id.
-
-## Step 3: Associate the key
-
-Call the CLI command with the resolved id and the Jira key:
-
-```
-assist backlog associate-jira <id> <JIRA-KEY> 2>&1
-```
-
-The command validates the key shape, fetches the issue to confirm it exists, prints its title, and stores the key. To remove an existing association instead, run:
-
-```
-assist backlog associate-jira <id> --clear 2>&1
-```
-
-Display the command output so the user can see the result. If the command reports an error (item not found, malformed key, or the issue could not be fetched), relay it to the user — no key is stored on failure.

package/claude/commands/update-jira.md

@@ -1,53 +0,0 @@
----
-description: Post a concise summary of this session's findings to a Jira ticket
-allowed_args: "[JIRA-KEY]"
----
-
-You are posting a concise comment summarising this session's findings to a Jira ticket via the Atlassian MCP. If a key is passed it is first attached to the session's current backlog item; otherwise the key is read from that item.
-
-## Step 1: Resolve the session's backlog item
-
-Determine the backlog item this session is working on — the one you are implementing, reviewing, or otherwise focused on (e.g. via `/next-backlog-item`, a `backlog run`, or earlier in this conversation). You need its id for the steps below.
-
-## Step 2: Resolve the Jira key
-
-If `$ARGUMENTS` contains a Jira key (matches `[A-Z]+-\d+`), attach it to the session's current backlog item, then use it:
-
-```
-assist backlog associate-jira <id> <JIRA-KEY> 2>&1
-```
-
-If the command reports an error (item not found, malformed key, or the issue could not be fetched), relay it to the user and stop — no key is stored on failure.
-
-If no key was passed, read it from the session item:
-
-```
-assist backlog show <id> 2>&1
-```
-
-Use the `Jira: <KEY>` line from the output.
-
-If no key can be resolved — none was passed and the item has no associated key (or there is no session item) — tell the user clearly that there is nothing to post to and do nothing further. Do not guess a key.
-
-## Step 3: Fetch the issue and resolve the comment target
-
-Fetch the issue with the `mcp__claude_ai_Atlassian__getJiraIssue` tool, requesting fields including `issuetype` and `parent`.
-
-If `fields.issuetype` indicates a sub-task (`fields.issuetype.subtask` is true), retarget the comment to the parent: use `fields.parent.key` as the issue you comment on. Otherwise comment on the key itself.
-
-## Step 4: Compose a concise comment
-
-Draft a terse summary of this session's findings from the conversation context:
-
-- One summary line stating what was done or found.
-- A few short bullets with the concrete specifics (files, decisions, outcomes).
-
-Keep it concise: no headers, no wall of text, no restating the whole session. If there is little of substance to report, keep it to the single summary line.
-
-Do not mention `assist`, the assist backlog, or any backlog item number in the comment — the Jira ticket is outward-facing and must not leak internal tooling references. Refer to commits, PRs, or the work itself instead.
-
-## Step 5: Preview and confirm before posting
-
-Show the drafted comment and the target issue key to the user. Do not post until the user explicitly confirms. If they ask for edits, revise and show the updated draft again.
-
-Once confirmed, post it with the `mcp__claude_ai_Atlassian__addCommentToJiraIssue` tool, using the resolved target key and `contentFormat: markdown`. Display the result so the user can see it landed.