@knpkv/jira-clockify 1.0.0 → 1.0.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@knpkv/jira-clockify",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "description": "TUI for Jira-Clockify time tracking, attachable to neovim",
   "license": "MIT",
   "author": "knpkv",
@@ -23,11 +23,11 @@
     "@opentui/react": "https://pkg.pr.new/anomalyco/opentui/@opentui/react@367a94087821b3b5feedd35bbb57df43b10a286e",
     "effect": "4.0.0-beta.87",
     "react": "^19.2.7",
-    "@knpkv/atlassian-common": "^0.3.0",
+    "@knpkv/agent-skills": "^0.2.2",
+    "@knpkv/atlassian-common": "^1.0.0",
     "@knpkv/clockify-api-client": "^0.3.0",
     "@knpkv/jira-api-client": "^0.3.0",
-    "@knpkv/jira-cli": "^1.0.0",
-    "@knpkv/agent-skills": "^0.2.1"
+    "@knpkv/jira-cli": "^1.1.1"
   },
   "devDependencies": {
     "@effect/vitest": "4.0.0-beta.87",

package/skills/jcf/SKILL.md

@@ -11,6 +11,7 @@ Use the `jcf` binary to manage Jira-backed Clockify timers.
 
 - Configure both services before timer operations: Jira OAuth and Clockify API key.
 - Use `jcf auth status` to check readiness.
+- `jcf` uses the shared Jira CLI auth profile store; for multi-site Jira accounts, use `jira auth profiles` and `jira auth use <profile>` before timer operations when the `jira` binary is available. When the `atlassian` binary is available, prefer `atlassian profiles doctor` to confirm that Jira Clockify is using the intended `jira-cli` auth store and `atlassian auth refresh` for expired Jira tokens.
 - Timer operations write to Clockify and may write Jira worklogs; confirm ambiguous ticket keys, durations, dates, and comments before running them.
 - Use `jcf issue list --json` when an agent needs structured ticket data.
 
@@ -22,6 +23,9 @@ jcf auth jira create
 jcf auth jira configure
 jcf auth jira login
 jcf auth clockify setup
+
+atlassian profiles doctor
+atlassian auth refresh
 ```
 
 Configure defaults:
@@ -85,5 +89,6 @@ jcf timer edit
 
 1. Run `jcf auth status` and `jcf timer status` before changing timer state.
 2. Use `jcf issue list --json` to resolve issue keys when the user gives a vague ticket description.
-3. Prefer explicit flags for non-interactive work: issue key, duration, date, time, project id, billable flag, and comment.
-4. If no timer is running, `jcf timer stop` may offer an interactive correction interval; use `jcf timer log` for deterministic manual logging.
+3. Verify the active Jira profile when the user names a Jira site/account or before posting worklogs; `atlassian profiles doctor` shows Jira Clockify as a consumer of the `jira-cli` auth store.
+4. Prefer explicit flags for non-interactive work: issue key, duration, date, time, project id, billable flag, and comment.
+5. If no timer is running, `jcf timer stop` may offer an interactive correction interval; use `jcf timer log` for deterministic manual logging.